gcc: permanent sandbox violations

[knittel]

Hello,

When trying to "emerge -e system" gcc would always fail with an access violation. I am having this problem for three weeks now.
I tried to completely clear my /usr/portage dir and also /var/cache/*. No change.

Anyone has an Idea what could be wrong or how to fix it (besides reinstall) ? Or what doku I may have overlooked ?


Here's the log:


/data/lokal/portage/build/portage/gcc-3.2.1-r6/image/usr/i686-pc-linux-gnu/gcc-bin/3.2/gcc

>>> Completed installing into /data/lokal/portage/build/portage/gcc-3.2.1-r6/image/


--------------------------- ACCESS VIOLATION SUMMARY ---------------------------LOG FILE = "/tmp/sandbox-gcc-3.2.1-r6-15915.log"

chown: /var/cache/edb
chown: /var/cache/edb/dep
open_wr: /var/cache/edb/mtimedb
chown: /var/cache/edb
chown: /var/cache/edb/dep
open_wr: /var/cache/edb/mtimedb
chown: /var/cache/edb
chown: /var/cache/edb/dep
open_wr: /var/cache/edb/mtimedb
chown: /var/cache/edb
chown: /var/cache/edb/dep
open_wr: /var/cache/edb/mtimedb
chown: /var/cache/edb
chown: /var/cache/edb/dep
open_wr: /var/cache/edb/mtimedb
--------------------------------------------------------------------------------

[rac]

Does "emerge -u --nodeps portage" help, as described in Can't emerge -u world, Access Violation?
_________________
For every higher wall, there is a taller ladder

[knittel]

Hello,

thanks fur your help. Unfortunately, I read it too late, ruined my system before with trying to simply emerge portage.

A fresh installl seems to fix it, however. Though emerge -e sytem still has issues.