amd64 would like to re-enable the multilib USE flag from 2008.0 going forward. It's not to replace functions from multilib.eclass, instead it's to be used in global scope(see nvidia-drivers and ati-drivers bugs for examples). For default/linux/amd64/2008.0 it should be forced on, with the no-multilib profile forced off. It would be nice if we can prevent the end user from messing with the flag(use.force?) Cardoe will be verifying that a change won't have a negative effect in the tree. From talking things over, we believe that it should have no negative effect but that media related ebuilds might need to be double checked for custom logic.
the following packages appear to have IUSE=multilib: media-video/captury media-libs/libcaptury sys-libs/newlib sys-libs/libstdc++-v3 sys-libs/glibc The following have IUSE=multilib but expect the functionality as described by this bug. x11-drivers/nvidia-drivers x11-drivers/ati-drivers Essentially the idea for USE=multilib is similar to USE=test, when it's a multilib profile USE=multilib will always be on. When it's not, it'll always be off. This is necessary for the changes in RDEPEND/DEPEND.
(In reply to comment #1) > the following packages appear to have IUSE=multilib: Also sys-devel/gcc [dleverton@shiny-one ~] $ inquisitio -r gentoo -k IUSE multilib --all-versions --compact * media-libs/libcaptury Captury Framework Library * media-video/captury Captury Tool - captures the screen from your OpenGL games/applications. * sys-devel/gcc The GNU Compiler Collection. Includes C/C++, java compilers, pie+ssp extensions, Haj Ten Brugge runtime bounds checking * sys-libs/glibc GNU libc6 (also called glibc2) C library * sys-libs/libstdc++-v3 Compatibility package for running binaries linked against a pre gcc 3.4 libstdc++ * sys-libs/newlib Newlib is a C library intended for use on embedded systems * x11-drivers/ati-drivers Ati precompiled drivers for recent chipsets * x11-drivers/nvidia-drivers NVIDIA X11 driver and GLX libraries
eh. you beat me to it. I was going to say I missed gcc.
OK. I've done this in the snapshot-tree, for the features/multilib profile, and it is forced off on the 32bit-native and 64bit-native (AKA no-multilib) profiles.
Since I upgrade to 2008 profile ( multilib ) I am getting this error * Building GLIBC with NPTL... make -r PARALLELMFLAGS="-j2" CVSOPTS="" -C /var/tmp/portage/sys-libs/glibc-2.6.1/work/glibc-2.6.1 objdir=`pwd` all make[1]: Entering directory `/var/tmp/portage/sys-libs/glibc-2.6.1/work/glibc-2.6.1' Makerules:47: *** Recursive variable `PATH' references itself (eventually). Stop. make[1]: Leaving directory `/var/tmp/portage/sys-libs/glibc-2.6.1/work/glibc-2.6.1' make: *** [all] Error 2 * * ERROR: sys-libs/glibc-2.6.1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3433: Called eblit-run 'src_compile' * environment, line 1128: Called eblit-glibc-src_compile * src_compile.eblit, line 168: Called src_compile * environment, line 3433: Called eblit-run 'src_compile' * environment, line 1128: Called eblit-glibc-src_compile * src_compile.eblit, line 179: Called toolchain-glibc_src_compile * src_compile.eblit, line 122: Called die * The specific snippet of code: * make PARALLELMFLAGS="${MAKEOPTS}" || die "make for ${ABI} failed" * The die message: * make for x86 failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/environment'. Could it be a bug with multilib use flag?
No. You're environment is jacked. Run env-update and check your environment. Also source /etc/profile. Basically you got a message to do that at some point during compiling some packages and didn't stop to do that.
Well, this has been done. My suggestion to the amd64 team is to deprecate *all* profiles prior to the 2008.0 profiles, for removal.
