On Wed, 03 Apr 2013 11:40:31 +0200 Thomas Sachau wrote: > Michał Górny schrieb: > > The first patch changes the eclass logic. The abi_* values, with 'abi_' > > prefix stripped, are called MULTILIB_ABI now. They are used to run > > the 'foreach' functions, and now are set in the called functions along > > with ABI. > > > > [...] > > > > Additionally, the 'default' fallback no longer calls > > multilib_toolchain_setup. This should improve compatibility with > > multilib-portage and *maybe* cross-compiling. > > You know, that multilib-portage does use MULTILIB_ABI as USE-expanded > variable? Using exactly the same in the eclass will call for collision > issues. Ok, I see one more issue. Whenever ebuilds start checking MULTILIB_ABI or the new-named equivalent of it, multilib portage is going to fail those checks by using 'default'. Any suggestions how to avoid that? Probably achievable only through staying with $ABI. -- Best regards, Michał Górny