On Thu, Nov 6, 2008 at 4:02 PM, Peter Humphrey <[EMAIL PROTECTED]> 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.
/usr/libexec/gcc/i686-pc-linux-gnu/ld: crt1.o: No such file: No such file or directory Could you try locate crt1.o ? By the way, why are you using gcc 4.2? I would either stick with the stable gcc 4.1 or use gcc 4.3 (which is used by a number of recent distributions, is used even in Debian Lenny - which should be released shortly - and has a number of improvements)
