On Sat, November 15, 2014 11:42 pm, Fernando de Oliveira wrote:
> On 14-11-2014 03:39, Bruce Dubbs wrote:
>
>> Pierre Labastie wrote:
>>
>>> Le 14/11/2014 03:21, Christopher Gregory a écrit :
>>>
>>>> Hello,
>>>>
>>>>
>>>> Why has the required instructions for adding shell=/bin/bash been
>>>> removed from the firefox page? This is a requirement for building in
>>>> chroot that was there but it seems that someone who perhaps did not
>>>> like having it in there deleted it just prior to the last release.
>
> Christopher, I don't know where you lokked at, but it is still in the
> page:
>
>
> {{{
> Compile Firefox by issuing the following commands:
> [Note]
> Note
>
>
> If you are compiling Firefox in chroot, make sure you have $SHELL
> environment variable set or prepend SHELL=/bin/sh. }}}
>
>
> I went there to modify according to your wish and noticed that.
>
>
>>>>
>>>> I have confirmed yet again that without that on a clean new
>>>> installation that if you are building in chroot it is required.
>>>>
>>>> It would be nice for it to be re-added and for all editors to leave
>>>> it alone when it is back.
>>>>
>>>> The only other solution I have to this is by adding more work for
>>>> myself and each time a new version of firefox comes out to update it
>>>> myself and not merge the changes from trunk.
>
> Believe me, I want to help you to succeed. have even privately asked
> someone what I could do to help you.
>
>>>>
>>> Doesn't the /etc/shells (which is now in LFS development) file help?
>>> Or
>>> maybe you could add the SHELL variable to your chroot environment?
>>> Instructions in the BLFS book are not aimed at building in chroot (I
>>> think it is mentioned somewhere). So, why add an instruction, which is
>>> only needed in that case? (I am not the person who removed the
>>> instruction, though).
>>
>> Fernando did the update of FF, but I did the one for LFS. We discussed
>> and felt it was not needed.
>>
>> I don't build in chroot, but via ssh and it's certainly ok there.
>>
>
>
> However, the modification of using
>
>
> test $(uname -m) = "i686" && sed -i 's/enable-optimize/&=-O2/' mozconfig
> || true
>
>
> was modified by Bruce. Didn't it work for you? If you update gcc to the
> one in the book (4.9.2), it is not even required anymore.
>
>
> --
> []s,
> Fernando
> --
Hello,
Sorry for the somewhat delayed responce to this. I found that in the
published version of stable systemd that it is not displayed. I later
found that it was still included in the xml but commented out.
My checking was also prompted by a support posting to the list that they
could not compile firefox without it and I found the exact same thing
myself. I had not realised at the time that I replied that it had been
commented out and I suggested that they follow the instructions carefully
as it looked like they were building in chroot.
It made my reply to them incorrect, as they were following the printed
instructions, but I beleive that they had deviated from some of the other
instructions as they said that they were not building in chroot. I know
that the SHELL=/bin/sh is not actually needed in a normally booted system.
The problem I have is that I have worked both 1st, 2nd and 3rd level
support roles, with 3rd level being only dealing with staff who could not
fix the customers errors. I find that having instructions that are not
needed normally, but in certain conditions do actually cut down some of
the support requests. Though there are prime examples of people on these
lists who are incapable of actually following instructions and post
support requests for every little thing that they have issues with, which
in some cases is every package they install. It is those type of people
ie the 1/2 percent or so that caused me to leave working at a call centre.
Please note that I am not trying to get at any of the editors past or
present. I am just pointing things out from a purely technical point of
view based on my own support role experiences.
By no means do I know everything, but I do know how to research and try
and fix my own errors and only then after I fail, and can not see how to
fix it do I post to a list such as this. At times I do find the solution
shortly after posting and having a break from it. I am just trying to
keep the book instructions correct, as I know that everyone is also trying
to do.
I do not know everyone of the current editors background, as for the most
part I do not directly ask, as I do not want to seem rude by appearing to
be prying.
We all have different ideas of how things should be in the book and for
the most part I just merge changes. If I feel strongly on it, like I did
for this issue, then I post. I do not expect TRUNK to always be changed
due to my own preferences. That is why I did re-add the chroot
instructions to the systemd branch and changed the .xml page to one
specific to the systemd branch so that it would not get lost. I now also
see that yet another version of firefox is out since my update to 33.0.3
in the book.
Regards,
Christopher.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
