On Monday 19 October 2009 18:53:10 Robin H. Johnson wrote:
> On Mon, Oct 19, 2009 at 11:02:50PM +0200, Thomas Sachau wrote:
> > > Is there any specific reason you're using the content of the
> > > LIBDIR_${ABI} variable? Maybe using the $ABI string as the USE flag
> > > would be better, in some form of USE_EXPAND manner (cannot use them raw
> > > as I believe we still have some code in the form of 'use $ARCH', which
> > > might not behave sanely if say both amd64 and x86 were set.
> > >
> > > Egs:
> > > multilib AMD64:
> > > USE="abi_x86 abi_amd64"
> > >
> > > Multilib PPC64:
> > > USE="abi_ppc abi_ppc64"
> > >
> > > Multilib MIPS (SGI hardware)
> > > USE="abi_n32 abi_n64"
> > >
> > > Possible valid multilib sets on MIPS are:
> > > [n32,n64] - at least one Gentoo system like this has been built.
> > > [o32,o64]
> > > [eabi,meabi] - docs fuzzy
> > > [nubi]
> >
> > I dont mind using some other string here. So those USE flags would be
> > fine for me. They could be USE_EXPANDed to e.g. for multilib amd64
> > ABI="x86 amd64"
>
> I just one thought overnight on it, are we going to have a namespace
> conflict with the variable?
>
> make.defaults already uses ABI= to contain a single value, not be
> multi-valued.ABIS or EABIS -mike
signature.asc
Description: This is a digitally signed message part.
