From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg
Date: Sat, 14 Jun 2014 21:10:06 -0500 [thread overview]
Message-ID: <539D007E.9080102@gmail.com> (raw)
In-Reply-To: <539CF4DD.7030708@cox.net>
John Campbell wrote:
> On 06/14/2014 05:12 PM, Dale wrote:
>>
>> media-libs/openjpeg:0
>>
>> (media-libs/openjpeg-1.5.1:0/0::gentoo, ebuild scheduled for merge)
>> conflicts with
>> >=media-libs/openjpeg-1.3-r2:0[abi_x86_64(-)] required by
>> (media-video/ffmpeg-2.2.3-r1:0/52.55.55::gentoo, installed)
>
> The multilib stuff is a work in progress... You have two 64bit ABIs
> set up, and ffmpeg wants the x32 rather than the 64. It needs it's
> libraries to match. Looks like openjpeg chose the 64 ABI to compile.
>
> Just set ABI_X86="32 x32" for openjpeg. It's in
> /etc/portage/env/media-libs/openjpeg-1.3-r2
>
>
>
I don't have a env directory in /etc/portage and there is no
openjpeg-1.3-r2 available in the tree. I sort of think I know what you
are talking about tho. I need to create that directory structure for
openjpeg-1.4-r1 and put ABI_X86="32 x32" in the file. My question is,
will this eventually be fixed in the tree and the error go away? I've
never put anything in the env directory before and would prefer to keep
it that way because I will forget it is there and it will come back and
bite me some day. Ask anyone here. lol
Now I see why the error didn't make any sense to me. I usually look for
something like a USE flag conflict or something. I don't recall ever
running into a 64/32 bit thingy before. O_O
Thanks. Muddy water is starting to clear up, a little bit anyway.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
next prev parent reply other threads:[~2014-06-15 2:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 21:23 [gentoo-user] Dependency conflict. openjpeg ffmpeg Dale
2014-06-14 23:00 ` Alan McKinnon
2014-06-15 0:12 ` Dale
[not found] ` <EQDB1o00e1kktTk01QDC7q>
2014-06-15 1:20 ` John Campbell
2014-06-15 2:10 ` Dale [this message]
[not found] ` <ESAJ1o00S1kktTk01SAKbb>
2014-06-15 2:31 ` John Campbell
2014-06-15 5:10 ` Dale
2014-06-15 8:46 ` Neil Bothwick
2014-06-15 8:59 ` Dale
2014-06-15 9:09 ` Neil Bothwick
2014-06-15 10:29 ` Dale
[not found] ` <EVAt1o00G1kktTk01VAu3p>
2014-06-15 6:13 ` John Campbell
2014-06-15 6:40 ` wraeth
2014-06-15 6:56 ` wraeth
2014-06-15 8:47 ` Dale
2014-06-16 7:43 ` [gentoo-user] " Jonathan Callen
2014-06-17 23:43 ` [gentoo-user] " Dale
2014-06-19 22:03 ` Dale
2014-06-17 15:56 ` thegeezer
2014-06-17 21:10 ` Dale
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=539D007E.9080102@gmail.com \
--to=rdalek1967@gmail.com \
--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