On Saturday 09 September 2006 22:57, "Mark Knecht" <[EMAIL PROTECTED]> wrote about 'Re: [gentoo-amd64] After gcc upgrade, sandbox won't configure (was: Re: gcc-4.1.1 update - emerge -eav world necessary?)': > 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?': > > > 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.
Okay, I figured you had, just didn't remember you mentioning it and I didn't want to forget a troubleshooting step. > > Looked at your config.log and the original config.log and I'd say you > > are actually hitting a slightly different issue. > > 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. Yeah, I thought about suggesting that as a workaround, but I was sort of hoping that output would tell me what was causing sandbox to behave so poorly. > > 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. > > Could you please > > post the output of root running: > > gcc-config -l > > binutils-config -l > > eselect compiler list > > and > > eselect binutils list > > If you need any of the info requested above > then let me know and I'll post it back sometime tomorrow. Nah, we worked though your problem, so I'm willing to let good enough alone. It's rather unlikely I could figure out what's wrong with portage/sandbox anyway; I just don't think I know enough about their internals. > I'm moving > along with the emerge -eav system which I restarted to ensure it went > all the way through without error. Very good; If it breaks again (it shouldn't; knock on wood) we'll try and fix it again. -- "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
pgppgs8XT3Zwq.pgp
Description: PGP signature
