On 11/02/2014 04:52 AM, Pierre Labastie wrote:
@Richard: xterm does not set the SHELL environment variable if the shell is not listed in the /etc/shells file (see "man xterm"). It only sets XTERM_SHELL in that case. So, several solutions: export SHELL=$XTERM_SHELL before running firefox building instructions, or as you already found out, SHELL=/bin/sh make... or create the /etc/shells file (Chapter 3 of the BLFS book), and restart xterm. Pierre
Thanks for your help. I hope it is ok to expand some more on this topic. I do not have an /etc/shells file, and I am trying to build firefox in an xterm (but not in a chroot environment). Nevertheless, if I type: echo "$SHELL" or: echo "$XTERM_SHELL", I get the same result: /bin/bash, which is where the bash program is located. With that setting for SHELL, if I use the make -f client.mk command in the firefox build, I get the "Python is not sane" error that I reported previously. However, using the SHELL=/bin/sh make -f client.mk command (and disabling gstreamer, as was pointed out earlier), the compilation proceeds. (It is not done yet, but at least it gets past any errors early on). On my system, if I type: ls -l /bin/sh, I find that it is a link as follows: /bin/sh -> bash So with SHELL set to /bin/bash the firefox build reports an error, but with SHELL set to just bash, it proceeds. I don't understand why it works in one case and not the other, but I hope this information might be useful. Richard -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
