Yikes! This is still happening with gcc-4.1.1-r3. Everything else works
fine. I haven't had any problems with installing and updating. Today I did
a emerge --update --deep --newuse system. I noticed GCC at the bottom of
the list, but figured maybe it was an anomaly before. Still no go.
I'm going to continue to just manually install the files from the sandbox
image, which oddly enough works just fine. I seem to be the only person
having this problem!
... HH
On 10/30/06, Francesco Talamona <[EMAIL PROTECTED]> wrote:
On Monday 30 October 2006 20:19, Hemmann, Volker Armin wrote:
> you have experienced it. You just don't see it. Somewhere in your
> filesystem are files, that should not be there. Files, that portage
> does not know about and that won't be removed, when the package gets
> uninstalled.
I ran findcruft some months ago, and it found some cruft around, but
nothing really dangerous. Of course was impossible to track back every
mud spot...
> If a package does not build with sandbox, it is broken. Open a bug.
Anyway, I just followed your advice and unset "-sandbox" fom my
FEATURES. I really don't need it (anymore).
If anything tries to escape its sandbox should be considered potentially
dangerous, lesson learned.
Thanks
Francesco
--
Linux Version 2.6.18-gentoo-r1, Compiled #1 PREEMPT Wed Oct 18 22:52:55
CEST 2006
One 1.8GHz AMD Athlon 64 Processor, 2GB RAM, 3607.13 Bogomips Total
aemaeth
--
[email protected] mailing list
--
Harry Holt, PMP
