1 |
Mick <michaelkintzios <at> gmail.com> writes: |
2 |
|
3 |
> > Your problem is different but has been covered in previous threads, as |
4 |
> > well as the news item. You could add ABI_X86="32 64" to make.conf, but |
5 |
> > that won't fit in with your desire for minimalism. So you need to run |
6 |
> > emerge with --autounmask-write then run etc-update or equivalent to |
7 |
> > apply the changes to package.use. |
8 |
> |
9 |
> Only to add that maintainers are regularly updating packages and this is why |
10 |
> you may find that suddenly new packages require USE="abi_x86_32", when a week |
11 |
> ago they didn't. |
12 |
> |
13 |
> It is worth noting that one multilib box of mine has not asked me (yet) to |
14 |
set |
15 |
> USE="abi_x86_32" on any of its packages, while my laptop is regularly |
16 |
> prompting me to do so. I have concluded that the former has no packages |
17 |
which |
18 |
> are using 32bit code, while the latter does (I know that at least Skype is a |
19 |
> culprit). |
20 |
> |
21 |
> So in extremis you could I guess purge any 32bit coded packages from your PC |
22 |
> and the "abi_x86_32" prompts should leave you alone. I shouldn't forget to |
23 |
> add your usual disclaimer: "YMMV" |
24 |
> |
25 |
|
26 |
Well, here are my extensions found in the make.conf, of interests:: |
27 |
|
28 |
EMERGE_DEFAULT_OPTS="--with-bdeps y --autounmask-write y" |
29 |
|
30 |
It been in there a while. However, I must "fess up" that often |
31 |
it does not work and i have to issue --autounmask-write manually followed up |
32 |
by etc-update. |
33 |
|
34 |
Maybe I need to do this all at once, but for @system or something? |
35 |
|
36 |
I did not want to build all of those 32 bit libraries, but maybe that |
37 |
is necessary? How can I get the listing of packages that need those 32 bit |
38 |
libs? Maybe that the way to go? It just seems like I keep cleaning this |
39 |
up over and over again. |
40 |
|
41 |
|
42 |
James |