On Fri, Mar 27, 2020 at 06:34:17PM +0100, Pierre Labastie via blfs-dev wrote: > On Fri, 2020-03-27 at 16:02 +0000, Ken Moffat via blfs-dev wrote: > > The thread Python multiprocessing checks in chroot is getting long > > and widening to cover how /dev/shm is treated in LFS. > > > > What I'd like to do is put the following note in the BLFS > > mozilla-derived packages where shm needs to be mounted when the > > package is configured: > > > > - - - > > If you are compiling this package in chroot you must do two things: > > > > First, as the root user, ensure that /dev/shm is mounted: > > > > mountpoint /dev/shm >/dev/null || mount -t tmpfs devshm /dev/shm > > > > If you do not do this, configuring will fail with a python traceback > > report referencing a > > /usr/lib/pythonN.N/multiprocessing/synchronize.py > > file. > > > > Second, as your normal user either ensure the $SHELL environment > > variable is set to /bin/sh, or prepend SHELL=/bin/sh. > > - - - > > > > Is that acceptable to everyone ? > > > > > > Sorry for arguing again. The problem is that SHELL needs to be > _exported_. It can be set to /bin/bash without problem. And for me, it > is not exported for _root_ after entering chroot (but it is set): > ---- > root [ / ]# echo $SHELL > /bin/bash > root [ / ]# env | grep SHELL > root [ / ]# > ---- > Now when doing su - <user> > ---- > pierre [ ~ ]$ echo $SHELL > /bin/bash > pierre [ ~ ]$ env | grep SHELL > SHELL=/bin/bash > pierre [ ~ ]$ > ---- > So no need to set/export anything as a user. And SHELL only needs to be > exported as root. > Pierre >
I'm puzzled by that - if it is not set, the configure breaks. Does SHELL also get queried when root is running the install ? ĸen -- When alle is ſayed and all is done, ye must chooſe your faces wisely, for soon enouff ye will be playing with fyre." The Nice and Accurate Prophecies of Agnes Nutter, Prophecy 5004 -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
