| Summary: | sys-devel/gcc-4.1.2: Can't compile on quad-core xeon x86_64 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Dominik Dorn <dominik.dorn> |
| Component: | [OLD] GCC Porting | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED INVALID | ||
| Severity: | major | CC: | rhill |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
/etc/make.conf
emerge --info /var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log bzip compressed /var/tmp/portage/sys-devel/gcc-4.1.2/work/build/config.log /proc/cpuinfo complete log of emerge All the config.log files in the build-dir (find . -name config.log) |
||
Created attachment 142731 [details]
/etc/make.conf
my make.conf, tried compiling with march=nocona and march=native... both didn't work
Created attachment 142733 [details]
emerge --info
Created attachment 142734 [details]
/var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log bzip compressed
Created attachment 142736 [details]
/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/config.log
Created attachment 142738 [details]
/proc/cpuinfo
Portage 2.1.3.19 (default-linux/amd64/2007.0, gcc-4.1.1, glibc-2.5-r0, 2.6.22-gentoo-r8 x86_64) ================================================================= System uname: 2.6.22-gentoo-r8 x86_64 Intel(R) Xeon(R) CPU E5345 @ 2.33GHz Timestamp of tree: Tue, 05 Feb 2008 07:00:01 +0000 app-shells/bash: 3.2_p17-r1 dev-java/java-config: 1.3.7, 2.0.33-r1 dev-lang/python: 2.4.4-r6 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.10-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.61-r1 sys-devel/automake: 1.9.6-r2, 1.10 sys-devel/binutils: 2.18-r1 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.24 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=native -O2 -pipe -v" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" -march=native wasn't added until gcc-4.2 so you'll get errors with that. -march=nocona should work. this config.log looks cut off. there should be a lot more than that. also what's the output of gcc -v? Created attachment 142761 [details]
complete log of emerge
emerge -u gcc > compile
hmm.. yes looks like the config.log is not complete, but that what's on the disc. i've changed the march back to nocona and did a new emerge which failed again.. attached it as compile.bz2 gcc -v is mybox gccbug # gcc -v Using built-in specs. Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.1.1-r3/work/gcc-4.1.1/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.1 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.1 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.1/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.1/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.1/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --enable-multilib --disable-libmudflap --disable-libssp --disable-libgcj --enable-languages=c,c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu Thread model: posix gcc version 4.1.1 (Gentoo 4.1.1-r3) thx for your help!! dominik you posted the wrong config.log ... gcc has multiple ones run `find -name config.log` in the build dir to find all the ones you need to post Created attachment 143109 [details]
All the config.log files in the build-dir (find . -name config.log)
hm... I've changed my /etc/make.profile to /usr/portage/profiles/default-linux/amd64/2007.0/no-multilib and now gcc compiles without problems. although emerge -upv world now tell's me I have to use grub-static, do I have to expect other problems? thanks for your help dominik if you're using non-multilib and have the wrong profile selected, things will fail not a gcc bug |
I'm trying to update gcc from version [4.1.1-r3] to 4.1.2 by doing emerge -uav gcc These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] dev-libs/gmp-4.2.2 [4.2.1-r1] USE="-doc -nocxx" 0 kB [ebuild U ] sys-devel/gcc-4.1.2 [4.1.1-r3] USE="fortran mudflap* (-altivec) -bootstrap -build -d% -doc -gcj -gtk (-hardened) -ip28 -ip32r10k (-multilib) -multislot (-n32) (-n64) -nls* -nocxx -objc -objc++ -objc-gc -test -vanilla" 0 kB [ebuild U ] sys-libs/glibc-2.6.1 [2.5] USE="-debug% -gd% -glibc-omitfp (-hardened) (-multilib) -nls* -profile (-selinux) -vanilla% (-build%) (-glibc-compat20%) (-nptl%*) (-nptlonly%*)" 0 kB gcc fails to build giving the error message posted bellow. Reproducible: Always Steps to Reproduce: 1.emerge gcc Actual Results: It looks like gcc builds itself one time, but the second time it does not work, I get the following error message Running configure in multilib subdirs 32 pwd: /var/tmp/portage/sys-devel/gcc-4.1.2/work/build/x86_64-pc-linux-gnu/libstdc++-v3 Running configure in multilib subdir 32 pwd: /var/tmp/portage/sys-devel/gcc-4.1.2/work/build/x86_64-pc-linux-gnu mkdir 32 configure: creating cache ./config.cache checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking target system type... x86_64-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for x86_64-pc-linux-gnu-gcc... /var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/xgcc -B/var/tmp/portage/sys- devel/gcc-4.1.2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /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/sys-devel/gcc-4.1.2/work/build' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build' make: *** [profiledbootstrap] Error 2 * * ERROR: sys-devel/gcc-4.1.2 failed. * Call stack: * ebuild.sh, line 1701: Called dyn_compile * ebuild.sh, line 1039: Called qa_call 'src_compile' * ebuild.sh, line 44: Called src_compile * ebuild.sh, line 1383: Called toolchain_src_compile * toolchain.eclass, line 26: Called gcc_src_compile * toolchain.eclass, line 1548: Called gcc_do_make * toolchain.eclass, line 1422: Called die * The specific snippet of code: * emake \ * LDFLAGS="${LDFLAGS}" \ * STAGE1_CFLAGS="${STAGE1_CFLAGS}" \ * LIBPATH="${LIBPATH}" \ * BOOT_CFLAGS="${BOOT_CFLAGS}" \ * ${GCC_MAKE_TARGET} \ * || die "emake failed with ${GCC_MAKE_TARGET}" * The die message: * emake failed with profiledbootstrap * * 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-devel/gcc-4.1.2/temp/build.log'. * Expected Results: mhm... compile.