From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: General weirdness - a tale of woe.
Date: Wed, 27 May 2015 21:25:01 +0000 (UTC) [thread overview]
Message-ID: <loom.20150527T231935-924@post.gmane.org> (raw)
In-Reply-To: 201505272131.25038.michaelkintzios@gmail.com
Mick <michaelkintzios <at> gmail.com> writes:
> > Your problem is different but has been covered in previous threads, as
> > well as the news item. You could add ABI_X86="32 64" to make.conf, but
> > that won't fit in with your desire for minimalism. So you need to run
> > emerge with --autounmask-write then run etc-update or equivalent to
> > apply the changes to package.use.
>
> Only to add that maintainers are regularly updating packages and this is why
> you may find that suddenly new packages require USE="abi_x86_32", when a week
> ago they didn't.
>
> It is worth noting that one multilib box of mine has not asked me (yet) to
set
> USE="abi_x86_32" on any of its packages, while my laptop is regularly
> prompting me to do so. I have concluded that the former has no packages
which
> are using 32bit code, while the latter does (I know that at least Skype is a
> culprit).
>
> So in extremis you could I guess purge any 32bit coded packages from your PC
> and the "abi_x86_32" prompts should leave you alone. I shouldn't forget to
> add your usual disclaimer: "YMMV"
>
Well, here are my extensions found in the make.conf, of interests::
EMERGE_DEFAULT_OPTS="--with-bdeps y --autounmask-write y"
It been in there a while. However, I must "fess up" that often
it does not work and i have to issue --autounmask-write manually followed up
by etc-update.
Maybe I need to do this all at once, but for @system or something?
I did not want to build all of those 32 bit libraries, but maybe that
is necessary? How can I get the listing of packages that need those 32 bit
libs? Maybe that the way to go? It just seems like I keep cleaning this
up over and over again.
James
prev parent reply other threads:[~2015-05-27 21:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 11:59 [gentoo-user] General weirdness - a tale of woe Peter Humphrey
2015-05-27 12:31 ` Canek Peláez Valdés
2015-05-27 13:02 ` Alan McKinnon
2015-05-27 13:09 ` Canek Peláez Valdés
2015-05-27 13:21 ` Rich Freeman
2015-05-27 14:16 ` Peter Humphrey
2015-05-27 20:40 ` Mick
2015-05-28 0:01 ` Peter Humphrey
2015-05-28 12:44 ` Rich Freeman
2015-05-28 13:49 ` Todd Goodman
2015-05-28 14:36 ` Peter Humphrey
2015-05-28 17:03 ` Peter Humphrey
2015-05-28 23:51 ` Rich Freeman
2015-05-29 0:10 ` Peter Humphrey
2015-05-29 8:25 ` Neil Bothwick
2015-05-29 9:13 ` Stephan Müller
2015-05-29 9:36 ` Peter Humphrey
2015-05-29 15:19 ` Mick
2015-05-29 15:28 ` Alan Grimes
2015-05-29 15:54 ` Mick
2015-05-29 23:20 ` Peter Humphrey
2015-05-30 9:00 ` Neil Bothwick
2015-05-30 11:49 ` Mick
2015-05-30 15:43 ` Peter Humphrey
2015-05-31 0:39 ` Peter Humphrey
2015-05-31 12:18 ` Mick
2015-05-31 14:01 ` Peter Humphrey
2015-05-31 14:25 ` Mick
2015-05-30 7:53 ` Alan McKinnon
2015-05-30 9:50 ` Peter Humphrey
2015-05-29 15:36 ` Peter Humphrey
2015-05-29 16:02 ` Mick
2015-06-01 17:28 ` Peter Humphrey
2015-05-27 23:40 ` Peter Humphrey
2015-05-27 18:38 ` [gentoo-user] " James
2015-05-27 20:09 ` Neil Bothwick
2015-05-27 20:31 ` Mick
2015-05-27 21:25 ` James [this message]
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=loom.20150527T231935-924@post.gmane.org \
--to=wireless@tampabay.rr.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