On 9/9/06, Boyd Stephen Smith Jr. <[EMAIL PROTECTED]> wrote:
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?
I did. No difference.
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
I will post these tomorrow if you'd like. I know you're quite deep
into this platform. None the less it seems I solved the problem, at
least for the evening. After searching through the forums I found a
number of people having the same problem. They were trying lots of
things to get it fixed. One of the things that kept coming up was old
gcc instances that should have been removed during previous gcc
upgrades but for one reason or another were not. Some folks said that
they fixed things by moving any instances of /usr/bin-i686-gcc* out of
that directory. I tried it and it seems to have worked for me. As soon
as I did that the emerge sandbox worked just fine. No other changes on
my system to move forward.
I'm not qualified to say why sandbox cared about this and no other
package seemed to, but it did seem to be the case.
Again, if you need any of the info requested above to look deeper
then let me know and I'll post it back sometime tomorrow. I'm moving
along with the emerge -eav system which I restarted to ensure it went
all the way through without error.
Thanks,
Mark
--
[email protected] mailing list
