Hi, I've noticed that the gcc profiles under /etc/env.d/gcc are created without GCCBITS=... As a result , in my case the /usr/bin/gcc32 and /usr/bin/gcc64 links to /usr/lib64/misc/gcc-config are not created after some investigation on the system i found toolchain.eclass is missing the following code: local mbits CC=$(XGCC) has_m32 && mbits="${mbits:+${mbits} }32" CC=$(XGCC) has_m64 && mbits="${mbits:+${mbits} }64" echo "GCCBITS=\"${mbits}\"" >> ${gcc_envd_file} was it removal intentional and if so what are the reasons to remove something that users depend on? Thanks Alex
*** Bug 181676 has been marked as a duplicate of this bug. ***
GCCBITS is dead
(In reply to comment #2) > GCCBITS is dead > What a comprehensive explanation. Maybe you can give some real explanation/reference to why GCCBITS was removed? And what its alternative? Since i can not manage to compile some 32 bit packages, with GCCBITS disabled, for example the following work only with GCCBITS enabled, even then i use x86_64-pc-linux-gnu-gcc32 instead of just gcc32: env CHOST="i686-pc-linux-gnu" CC="x86_64-pc-linux-gnu-gcc32" swi-prolog without GCCBITS it fails with: ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-mt --disable-gmp --enable-readline --enable-shared --disable-custom-flags --build=i686-pc-linux-gnu checking builddir... src checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc32 checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. while both: env CHOST="i686-pc-linux-gnu" CC="x86_64-pc-linux-gnu-gcc32" swi-prolog and: env CHOST="i686-pc-linux-gnu" CC="gcc32" swi-prolog works with GCCBITS enbaled. Thanks
there is nothing to it ... GCCBITS is dead code we're no longer supporting the solution is to use proper ABI CFLAGS like any other multilib setup
