| 1 |
Yikes! This is still happening with gcc-4.1.1-r3. Everything else works |
| 2 |
fine. I haven't had any problems with installing and updating. Today I did |
| 3 |
a emerge --update --deep --newuse system. I noticed GCC at the bottom of |
| 4 |
the list, but figured maybe it was an anomaly before. Still no go. |
| 5 |
|
| 6 |
I'm going to continue to just manually install the files from the sandbox |
| 7 |
image, which oddly enough works just fine. I seem to be the only person |
| 8 |
having this problem! |
| 9 |
|
| 10 |
... HH |
| 11 |
|
| 12 |
On 10/30/06, Francesco Talamona <ti.liame@×××××.it> wrote: |
| 13 |
> |
| 14 |
> On Monday 30 October 2006 20:19, Hemmann, Volker Armin wrote: |
| 15 |
> > you have experienced it. You just don't see it. Somewhere in your |
| 16 |
> > filesystem are files, that should not be there. Files, that portage |
| 17 |
> > does not know about and that won't be removed, when the package gets |
| 18 |
> > uninstalled. |
| 19 |
> I ran findcruft some months ago, and it found some cruft around, but |
| 20 |
> nothing really dangerous. Of course was impossible to track back every |
| 21 |
> mud spot... |
| 22 |
> |
| 23 |
> > If a package does not build with sandbox, it is broken. Open a bug. |
| 24 |
> Anyway, I just followed your advice and unset "-sandbox" fom my |
| 25 |
> FEATURES. I really don't need it (anymore). |
| 26 |
> |
| 27 |
> If anything tries to escape its sandbox should be considered potentially |
| 28 |
> dangerous, lesson learned. |
| 29 |
> |
| 30 |
> Thanks |
| 31 |
> Francesco |
| 32 |
> -- |
| 33 |
> Linux Version 2.6.18-gentoo-r1, Compiled #1 PREEMPT Wed Oct 18 22:52:55 |
| 34 |
> CEST 2006 |
| 35 |
> One 1.8GHz AMD Athlon 64 Processor, 2GB RAM, 3607.13 Bogomips Total |
| 36 |
> aemaeth |
| 37 |
> -- |
| 38 |
> gentoo-amd64@g.o mailing list |
| 39 |
> |
| 40 |
> |
| 41 |
|
| 42 |
|
| 43 |
-- |
| 44 |
Harry Holt, PMP |
Archives