-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Duncan wrote: > > Quoting the gist of the general instructions: > > Code Listing 2.1: Upgrading GCC > # emerge -uav gcc >
Ok, that is failing for me after a long time (probably on the second pass):
checking for x86_64-pc-linux-gnu-gcc...
/var/tmp/portage/gcc-4.1.1/work/build/./gcc/xgcc -B/var/tmp/po
rtage/gcc-4.1.1/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/
- -B/usr/x86_64-pc-linux-gnu/lib/ -isy
stem /usr/x86_64-pc-linux-gnu/include -isystem
/usr/x86_64-pc-linux-gnu/sys-include -m32
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C
compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
make[2]: *** [configure-target-libstdc++-v3] Error 1
make[2]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build'
make: *** [profiledbootstrap] Error 2
!!! ERROR: sys-devel/gcc-4.1.1 failed.
Call stack:
ebuild.sh, line 1539: Called dyn_compile
ebuild.sh, line 939: Called src_compile
ebuild.sh, line 1248: Called toolchain_src_compile
toolchain.eclass, line 24: Called gcc_src_compile
toolchain.eclass, line 1528: Called gcc_do_make
toolchain.eclass, line 1402: Called die
!!! emake failed with profiledbootstrap
!!! If you need support, post the topmost build error, and the call
stack if relevant.
Not sure what is going on here. That -m32 doesn't look good though (but
what do I know?).
I am able to compile both 64-bit and 32-bit in general (tested simple
shell of a .c file). And it compiled for a long time before dieing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFE+I/TG4/rWKZmVWkRAnqCAJoCT1Kkyfmn/LNAJH/5iLDUiSMoxgCgp9+M
7O2x7z9HDC9jqQJn3soMvB0=
=LCXU
-----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
