On Wed, 03 May 2017 13:02:14 +0200 Stephen Berman <[email protected]> 
wrote:

> On Tue, 2 May 2017 18:02:55 +0100 Ken Moffat <[email protected]> wrote:
>
>> I'm sure that at one time (when gtk3 was first usable) we noted that
>> both gtk2 AND gtk3 were needed.  Not sure why that dropped out -
>> maybe it was me - but the error message above is conclusive.  If it
>> was my fault that got removed: Sorry.
>
> No big deal, and thanks for confirming.
>
>> There are many things which still need gtk2.
>
> That's fine; I'm just trying to build only what I need.
>
>>> I note that after this failure, since I needed Firefox to pursue my
>>> normal workflow using LFS, I downloaded the firefox-52.0.2 binary
>>> package from the Mozilla website and have installed and been using it
>>> without serious problems, although my LFS does not have GTK+2 (however,
>>> the directory of the binary package includes a subdirectory gtk2
>>> containing libmozgtk.so).
>>> 
>>
>> I use the binary on my netbook, because recompiling there took a
>> whole day last time I tried it - everything is linked in.
>
> Yeah, the estimated build time of "14 SBU (with parallelism=4 on a
> recent intel i7, much longer on lesser CPUs)" is a bit intimidating;
> this is a rather old single-core machine, and the GCC test suite took
> 583 minutes...
>
>> But ff-51 has vulnerabilities.  I normally point people to the
>> development book, but I should add that there may be breakage from
>> time to time.
>>
>> For the future, if you install gtk2 you should be able to build
>> 52.1.0esr - moving to ff53 and later requires rustc.
>
> For the time being I have to stay below 53 anyway, since it appears not
> to support my card reader, unlike 52.1 (on another machine).

FTR, after building and installing GTK+2 I succeeded in building
firefox-52.1.0esr (took a mere 311 minutes ;-), and my card reader works
with it too.

Steve Berman
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to