1 |
On Sun, 2005-07-24 at 11:10 -0700, Bob Sanders wrote: |
2 |
> On Sun, 24 Jul 2005 17:06:49 +0200 |
3 |
> Richard Fish <bigfish@××××××××××.org> wrote: |
4 |
> |
5 |
> |
6 |
> > |
7 |
> > Argh, I don't get it. /u/p/p/default-linux/amd64/2005.0/use.mask |
8 |
> > contains "multilib", but with a comment stating it is forced on when |
9 |
> > MULTILIB_ABIS is defined, and make.defaults has MULTILIB_ABIS="x86 amd64". |
10 |
> > |
11 |
> > Can any AMD64 users shed some light on this please? |
12 |
> > |
13 |
> |
14 |
> multilib can be, or it used to be able to, turned off so that only 64-bit versions of the |
15 |
> libs get built. |
16 |
> |
17 |
> Normally, it should be turned on and set in the USE string, for most folks on a x86_64 |
18 |
> platform. But, on a system without multilib, turning it on means that, as a minimum an - |
19 |
> |
20 |
> emerge -uDav --newuse system |
21 |
> |
22 |
> will need to be performed to rebuild gcc, glibc and all the base system libs so that the following |
23 |
> get created - |
24 |
> |
25 |
> /lib64 |
26 |
> /lib32 |
27 |
> /usr/lib32 |
28 |
> /usr/lib64 |
29 |
|
30 |
All of those are present on my system, but I am still seeing |
31 |
"(-multilib)" when I do e.g. "emerge -va glibc". |
32 |
|
33 |
-- |
34 |
jules |
35 |
|
36 |
|
37 |
-- |
38 |
gentoo-user@g.o mailing list |