On Mon, Nov 03, 2014 at 01:47:48PM +0100, Pierre Labastie wrote: > Le 03/11/2014 12:31, Richard a écrit : > > > >before startx: > >------------------------ > >root:~# env | grep SHELL > >SHELL=/bin/bash > >----------------------- > > > >after startx: > >------------------------ > >root:~# env | grep SHELL > >XTERM_SHELL=/bin/bash > > > >but: > > > >root:~# echo "$SHELL" > >/bin/bash > >---------------------- > > > >Richard > Looks like one of your startup scripts creates the SHELL variable, but does > not export it... > > Pierre
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. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
