From: John Campbell <jdc.rpv@cox.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Dependency conflict. openjpeg ffmpeg
Date: Sat, 14 Jun 2014 23:13:13 -0700 [thread overview]
Message-ID: <539D3979.8020405@cox.net> (raw)
In-Reply-To: <EVAt1o00G1kktTk01VAu3p>
On 06/14/2014 10:10 PM, Dale wrote:
> John Campbell wrote:
>> On 06/14/2014 07:10 PM, Dale wrote:
>>
>>> 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.
>>
>> Sorry, I mistyped the version number.
>
> Ahh. I was curious and thought about that. That version is mentioned
> in the error tho so I wasn't sure. I wonder tho, can I add that file
> and not have a version at all? Sort of like I do in package.keywords
> etc etc.
Yes, you can skip the version number. It should be just like the
package.* directories but for env(ironment) variables. It wouldn't
suprise me if someone renamed it to package.env someday like they did
from package.keywords to package.accept_keywords.
> Well, I have 16Gbs here. I'm not lacking for memory. If memory prices
> were to drop a bit, I could upgrade some more. I'd have to swap out
> what I have tho. Old mobo would only take 4GB sticks and this new one
> will take 8GB sticks.
Unless you have a specific reason for keeping both x32 and 64 ABIs I'd
suggest changing to ABI_X86="32 64" globally in /etc/make.conf (or
/etc/portage/make.conf). It's a lot easier than waiting for the next
conflict. Then do "emerge --new-use --deep @world" and you're done.
There shouldn't bee too many packages that need rebuilding.
next prev parent reply other threads:[~2014-06-15 6:13 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
[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 [this message]
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=539D3979.8020405@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