On 6 Nov, Peter Humphrey wrote: > Hello, > > 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. >
The lines 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 look like a misconfigured gcc. Can you emerge any package which requires the C-compiler? Try gcc-config -l and look which gcc is selected and if you can select a different one. Then - with this one selected - reemerge the probably newer version of gcc which was broken. I hope this helps, Helmut. -- Helmut Jarausch Lehrstuhl fuer Numerische Mathematik RWTH - Aachen University D 52056 Aachen, Germany
