| 1 |
On Mon, Oct 19, 2009 at 11:02:50PM +0200, Thomas Sachau wrote: |
| 2 |
> > Is there any specific reason you're using the content of the |
| 3 |
> > LIBDIR_${ABI} variable? Maybe using the $ABI string as the USE flag |
| 4 |
> > would be better, in some form of USE_EXPAND manner (cannot use them raw |
| 5 |
> > as I believe we still have some code in the form of 'use $ARCH', which |
| 6 |
> > might not behave sanely if say both amd64 and x86 were set. |
| 7 |
> > |
| 8 |
> > Egs: |
| 9 |
> > multilib AMD64: |
| 10 |
> > USE="abi_x86 abi_amd64" |
| 11 |
> > |
| 12 |
> > Multilib PPC64: |
| 13 |
> > USE="abi_ppc abi_ppc64" |
| 14 |
> > |
| 15 |
> > Multilib MIPS (SGI hardware) |
| 16 |
> > USE="abi_n32 abi_n64" |
| 17 |
> > |
| 18 |
> > Possible valid multilib sets on MIPS are: |
| 19 |
> > [n32,n64] - at least one Gentoo system like this has been built. |
| 20 |
> > [o32,o64] |
| 21 |
> > [eabi,meabi] - docs fuzzy |
| 22 |
> > [nubi] |
| 23 |
> I dont mind using some other string here. So those USE flags would be fine for me. They could be |
| 24 |
> USE_EXPANDed to e.g. for multilib amd64 ABI="x86 amd64" |
| 25 |
I just one thought overnight on it, are we going to have a namespace |
| 26 |
conflict with the variable? |
| 27 |
|
| 28 |
make.defaults already uses ABI= to contain a single value, not be |
| 29 |
multi-valued. |
| 30 |
|
| 31 |
-- |
| 32 |
Robin Hugh Johnson |
| 33 |
Gentoo Linux: Developer, Trustee & Infrastructure Lead |
| 34 |
E-Mail : robbat2@g.o |
| 35 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives