From: John Campbell <jdc.rpv@cox.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compilation error mpv / libav
Date: Tue, 7 Nov 2017 21:04:45 -0800 [thread overview]
Message-ID: <0886619f-ae0c-4e3f-af33-8355a040e5f1@cox.net> (raw)
In-Reply-To: <XFrz1w00a1kktTk01Fs14Z>
> I installed ffmpeg-9999 and it compiles fines.
>
> Everything else failed again (for example mpv-9999).
>
> Why does an update of already ok installed applications
> break something in parts because the installation
> has components, which are mutually exclusive?
> They weren't before (whichout the update everythong was fine...)
I've been periodically fighting with mpv and ffmpeg for various reasons
for quite some time. Which is why I've been pushed into running live
versions of both. Version bumps on ebuilds that fail version checks
(like this one) is my first line of defence.
The reason live rebuilds keep breaking even though they're installed it
the upstream developers change to library requirements and flags without
telling anyone.
There's a bug report about this at https://bugs.gentoo.org/635650 which
seems to offer several solutions and satisfies none... It looks like
the decision at present is "wait and hope it gets fixed upstream"
next prev parent reply other threads:[~2017-11-08 5:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <XD2T1w03d1kktTk01D2UHa>
2017-11-08 3:21 ` [gentoo-user] Compilation error mpv / libav John Campbell
2017-11-08 3:51 ` tuxic
2017-11-08 7:28 ` [gentoo-user] " Nikos Chantziaras
[not found] ` <XFrz1w00a1kktTk01Fs14Z>
2017-11-08 5:04 ` John Campbell [this message]
2017-11-08 5:50 ` [gentoo-user] " R0b0t1
2017-11-08 1:01 tuxic
2017-11-08 1:38 ` R0b0t1
2017-11-08 2:41 ` tuxic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0886619f-ae0c-4e3f-af33-8355a040e5f1@cox.net \
--to=jdc.rpv@cox.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox