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