Armin K. wrote:
On 6.10.2014 21:50, Ken Moffat wrote:
I'm more interested in the circumstances which require SHELL to be
set. In the past I have built firefox several times in chroot -
sometimes I booted first to check it was ok, other times I did not
(some of those were test builds because of other changes, or even
the old LFS idea of "can it build itself ?"). I never found a need
to set SHELL=/bin/sh, but I probably have not done this for the best
part of a year.
Perhaps something in firefox changed ? What error results ?
One thing I always do is to ensure that /tools is no longer on my
PATH, maybe that might be the difference ?
I could neither confirm the issue. SHELL is set to /bin/bash when using
the chroot command from end of the chapter 6 in LFS. I built all mozilla
packages in chroot just fine without the workaround. I too remove the
/tools entirely before proeeding post LFS.
I wouldn't think that the presence of /tools would make any difference
if the chroot command in Section 6.73 - "Cleaning Up" is used. It's not
in the PATH. I use an alias:
alias lfs='sudo /usr/sbin/chroot /mnt/lfs /usr/bin/env -i HOME=/root
TERM="$TERM" PS1="\u:\w\\\\$ " PATH=/bin:/usr/bin:/sbin:/usr/sbin
/bin/bash --login'
(That's one line.)
I do note that `env` does not have SHELL defined, but it is present in
`set`.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
