Recent versions of portage have suggested an emerge -e world, so I thought
I'd try it. It got as far as sandbox, which failed with the once-common "C
compiler cannot create executables" error. Of course I
tried "FEATURES=-sandbox emerge sandbox" but that failed with the same
error.
I wondered what is set wrongly in my environment, so I booted a minimal
installation CD and chrooted into the system, but with the same result.
Can anyone suggest where my problem might lie? I've attached the log file.
I'm confused by the apparent references in it to the cross-compiler. Google
seems to have only old references.
This is a dual-Opteron box with a mostly-amd64 setup - only a few packages
are ~amd64. I'm also running an emerge -eq world on another amd64 box,
which has had no problem with sandbox. Same versions of portage and sandbox
on both machines.
--
Rgds
Peter
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by sandbox configure 1.2.18.1, which was
generated by GNU Autoconf 2.59. Invocation command line was
configure:1533: checking for a BSD-compatible install
configure:1588: result: /usr/bin/install -c
configure:1599: checking whether build environment is sane
configure:1642: result: yes
configure:1707: checking for gawk
configure:1723: found /bin/gawk
configure:1733: result: gawk
configure:1743: checking whether make sets $(MAKE)
configure:1763: result: yes
configure:1942: checking for i686-pc-linux-gnu-gcc
configure:1958: found /usr/bin/i686-pc-linux-gnu-gcc
configure:1968: result: i686-pc-linux-gnu-gcc
configure:2250: checking for C compiler version
configure:2253: i686-pc-linux-gnu-gcc --version </dev/null >&5
i686-pc-linux-gnu-gcc (GCC) 4.2.2 (Gentoo 4.2.2 p1.0)
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:2256: $? = 0
configure:2258: i686-pc-linux-gnu-gcc -v </dev/null >&5
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: /tmp/cross/i686-pc-linux-gnu/portage/cross-i686-pc-linux-gnu/gcc-4.2.2/work/gcc-4.2.2/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/i686-pc-linux-gnu/gcc-bin/4.2.2 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.2.2/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.2.2 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.2.2/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.2.2/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.2.2/include/g++-v4 --host=x86_64-pc-linux-gnu --target=i686-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 --disable-multilib --disable-libmudflap --disable-libssp --disable-libgcj --with-arch=i686 --enable-languages=c,c++,fortran --with-sysroot=/usr/i686-pc-linux-gnu --disable-bootstrap --disable-libgomp --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 4.2.2 (Gentoo 4.2.2 p1.0)
configure:2261: $? = 0
configure:2263: i686-pc-linux-gnu-gcc -V </dev/null >&5
i686-pc-linux-gnu-gcc: '-V' must come at the start of the command line
configure:2266: $? = 1
configure:2289: checking for C compiler default output file name
configure:2292: i686-pc-linux-gnu-gcc -march=opteron -O2 -pipe conftest.c >&5
/usr/libexec/gcc/i686-pc-linux-gnu/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure:2295: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME "sandbox"
| #define PACKAGE_TARNAME "sandbox"
| #define PACKAGE_VERSION "1.2.18.1"
| #define PACKAGE_STRING "sandbox 1.2.18.1"
| #define PACKAGE_BUGREPORT "sandbox@gentoo.org"
| #define PACKAGE "sandbox"
| #define VERSION "1.2.18.1"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2334: error: C compiler cannot create executables
See `config.log' for more details.