| 1 |
Well, I'm trying with gcc 4.1.1, not 4.1.1-r1 (it's masked), but if I can't |
| 2 |
get this to work I'll try that one. The problem is the 3-hour compile until |
| 3 |
the error shows up. I'm still unclear why the ebuild postinst / qmerge does |
| 4 |
not work - it doesn't seem to put everything in place like it should (still |
| 5 |
have broken libs, etc.). |
| 6 |
|
| 7 |
... HH |
| 8 |
|
| 9 |
On 10/28/06, Hemmann, Volker Armin <volker.armin.hemmann@××××××××××××.de> |
| 10 |
wrote: |
| 11 |
> |
| 12 |
> On Saturday 28 October 2006 07:02, Duncan wrote: |
| 13 |
> |
| 14 |
> > You /could/ try turning sandbox off (in FEATURES). That's a bit |
| 15 |
> dangerous |
| 16 |
> > by itself, but if you turn userpriv on at the same time, it should be |
| 17 |
> > fairly safe. |
| 18 |
> |
| 19 |
> NO! |
| 20 |
> |
| 21 |
> Just no! |
| 22 |
> |
| 23 |
> Never ever turn of sandbox. Without sandbox, files can end everywhere in |
| 24 |
> your |
| 25 |
> installation, destroying stuff, make apps segfault randomly - and the |
| 26 |
> worst, |
| 27 |
> portage does not know about them. |
| 28 |
> |
| 29 |
> Never ever turn of sandbox. And never tell others to do so. |
| 30 |
> btw |
| 31 |
> * sys-devel/gcc |
| 32 |
> Latest version available: 4.1.1-r1 |
| 33 |
> Latest version installed: 4.1.1-r1 |
| 34 |
> |
| 35 |
> and I have sandbox enabled. So it is not a sandbox problem. Something else |
| 36 |
> is |
| 37 |
> broken on his system. |
| 38 |
> -- |
| 39 |
> gentoo-amd64@g.o mailing list |
| 40 |
> |
| 41 |
> |
| 42 |
|
| 43 |
|
| 44 |
-- |
| 45 |
Harry Holt, PMP |
Archives