On Saturday 09 September 2006 19:29, "Mark Knecht" <[EMAIL PROTECTED]> wrote about 'Re: [gentoo-amd64] gcc-4.1.1 update - emerge -eav world necessary?': > I actually finished the first emerge -eav system. My gcc upgrade > failed. Apparently there has been some bug reports with the same > problems many months ago but no resolution. I don't know why it imacts > me. I don't have any cross-development stuff on my machine, although > reading a bit it appears that the AMD64 tool chain has some built in.
Yeah, it's actually a feature that, while it has caused a few issues, really helps when doing mixed amd64/x86 distcc-ing. I like it. > Anyway, here's the bug report showing where I'm stopped. > http://bugs.gentoo.org/show_bug.cgi?id=133209 I'm assuming you have tried turning off the sandbox feature while emerging sandbox, correct? Looked at your config.log and the original config.log and I'd say you are actually hitting a slightly different issue. Could you please post the output of root running: gcc-config -l binutils-config -l eselect compiler list and eselect binutils list -- "If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability." -- Gentoo Developer Ciaran McCreesh
pgpEjBgVVtx1C.pgp
Description: PGP signature
