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
