I'm building gentoo in a chroot, which is exported via NFS for diskless nodes. Emerging chromium failed with a cryptic message about python multiprocessing and permission denied, just as in the linked URL. The problem boiled down to /dev/shm not being mounted as tmpfs in the chroot environment. This is probably the case for any first-time gentoo installation from the live CD. Thus, I'm proposing to add a check to the ebuild, which complains if /dev/shm isn't mounted as tmpfs. Reproducible: Always Steps to Reproduce: 1.umount /dev/shm 2.emerge chromium
Please add your emerge --info and attach the build log.
I'm not near my machine now and I doubt, that this is a problem specific to my setup, however I'll attach them, of course asap. For the time being, please have a look at the URL, where you can find those files of somebody else having the very same problem.
I don't think it makes sense to add ebuild checks for every package that requires shared memory -- it's a standard Linux feature. Fix whatever documentation you are using to set up the chroot instead.
packages that need shared memory mounted are few and very far apart, sometimes a shared memory mount it's detrimental to the setup. Provided a check it's not too expensive it could be a good idea to add it.
(In reply to Francesco Riosa from comment #4) > packages that need shared memory mounted are few and very far apart, > sometimes a shared memory mount it's detrimental to the setup. Lots of stuff uses shared memory at runtime. It's just fairly rare for a package build system to use it. Having /dev/shm mounted is never "detrimental". If your Linux system does not have this mounted, your Linux system is broken, period.