Dear Jack,

I did the same with "su -" and changed to root and the result is still the same.

Any ideas what I did wrong ?


best, Tamerr


>>> Source compiled.
 * --------------------------- ACCESS VIOLATION SUMMARY ---------------------------  * LOG FILE: "/var/tmp/portage/dev-python/setuptools-44.1.0/temp/sandbox.log"
 *
VERSION 1.0
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line

F: open_wr
S: deny
P: /usr/local/lib/python3.7/lib2to3/Grammar3.7.7.final.0.pickle
A: /usr/local/lib/python3.7/lib2to3/Grammar3.7.7.final.0.pickle
R: /usr/local/lib/python3.7/lib2to3/Grammar3.7.7.final.0.pickle
C: python3.7 setup.py build -j 8

F: open_wr
S: deny
P: /usr/local/lib/python3.7/lib2to3/PatternGrammar3.7.7.final.0.pickle
A: /usr/local/lib/python3.7/lib2to3/PatternGrammar3.7.7.final.0.pickle
R: /usr/local/lib/python3.7/lib2to3/PatternGrammar3.7.7.final.0.pickle
C: python3.7 setup.py build -j 8
 * --------------------------------------------------------------------------------


Not sure if it's relevant here, but how are you getting root privs to run emerge?  I've seen similar problems because of environment variables set for the regular user which are not cleared by su or sudo.  I think I end up using "su -" when I run into that (although I admit it has been a long time since I did) or log in directly as root.

Jack


Reply via email to