On Mon, Nov 03, 2014 at 09:39:53PM +0000, Guy Dalziel wrote: > > I had the same issue when building Seamonkey: it claimed that my Python > installation wasn't sane. As soon as I exported SHELL=/bin/bash it > started compiling just fine. > > The solution to getting SHELL set properly is to populate /etc/shells: > > xterm without /etc/shells: > > bash-4.3$ printenv SHELL > bash-4.3$ > > populate /etc/shells: > > bash-4.3# cat > /etc/shells << EOF > > /bin/sh > > /bin/bash > > EOF > > xterm with /etc/shells: > > bash-4.3$ printenv SHELL > /bin/bash > bash-4.3$ > > I had to add both /bin/sh and /bin/bash before it would set my SHELL > variable.
I _think_ that supports what Pierre originally said, perhaps on blfs-dev, and what Bruce has now put into LFS. If it fixes things for some people, that is good, but I am still puzzled. What I do not understand is why I have never needed to touch this. I don't build seamonkey, but I build firefox (currently at 32.0.1 on this machine, built from a script which I ran from an rxvt-unicode term). Testing 'printenv SHELL' returns /bin/bash _without_ /etc/shells existing. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
