On Mon, Oct 06, 2014 at 12:30:38PM -0500, Bruce Dubbs wrote: > [email protected] wrote: > > >Log: > >restore note about SHELL envar in firefox instructions > > > >+ If you are compiling <application>Firefox</application> in chroot, > >make > >+ sure you have <envar>$SHELL</envar> environment variable set or > >prepend > > <envar>SHELL=/bin/sh</envar> to the first make command below. > > I'm not really opposed to leaving this in the book, but I question how > relevant it is. FF has a huge number of prerequisites and I question how > many people would get to it still in chroot. > > If on another system or vm, it is so much easier to just build ssh and work > from a full environment into a evolving BLFS via that then in chroot. > > If on a single system, it is easier to work from twm or other simple wm or > text mode browser than chroot. > > -- Bruce
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 ? ĸ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-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
