Failure to install on a fresh install due to sanbox violation. python3.4/usr/lib/python-exec/python3.4/pilfile.py to 755 [32;01m*[0m python3_4: running distutils-r1_run_phase python_install_all >>> Completed installing pillow-2.8.1 into /var/tmp/portage/dev-python/pillow-2.8.1/image/ [31;01m*[0m --------------------------- ACCESS VIOLATION SUMMARY --------------------------- [31;01m*[0m LOG FILE: "/var/log/sandbox/sandbox-32298.log" [31;01m*[0m 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: unlink S: deny P: /sys/fs/cgroup/si8lQs A: /sys/fs/cgroup/si8lQs R: /sys/fs/cgroup/si8lQs C: /usr/bin/python2.7 setup.py install --root=/var/tmp/portage/dev-python/pillow-2.8.1/image//_python2.7 F: unlink S: deny P: /sys/fs/cgroup/TbYhDs A: /sys/fs/cgroup/TbYhDs R: /sys/fs/cgroup/TbYhDs C: /usr/bin/python3.4 setup.py install --root=/var/tmp/portage/dev-python/pillow-2.8.1/image//_python3.4 [31;01m*[0m -------------------------------------------------------------------------------- Reproducible: Always
emerge --info please.
Created attachment 419102 [details] emerge.info.txt
Created attachment 419104 [details] build.log.txt
no idea what happens here.
(In reply to Justin Lecher from comment #4) > no idea what happens here. If it helps reproducing, I encountered this while in chroot from an ubuntu livecd, setting up a fresh install from stage 3 (20151210)
From the log: Exception installing mp_compile, proceeding without: [Errno 13] Permission denied Looking at mp_compile.py, it is trying to set up a multiprocessing pool. This requires that it create a semaphore for locking. This would normally be created by glibc in /dev/shm. However, your ubuntu chroot environment is probably broken in that you did not mount a tmpfs at that location. glibc then tries any other available tmpfs, which would lead it to /sys/fs/cgroup. This is a lot of guesswork, but I doubt there will be any better clues. Please check to make sure your chroot is properly configured.