On 05/27/2018 11:55 AM, Paul Rogers wrote:
OK, with rustc-1.25 installed cleanly I gave firefox-60.0.1 a go. It quickly
died because BLFS-8.1 has harfbuzz-1.4.8 and it wanted 1.7.6. I shut down and
slept on it. So here are my options as I see them, not necessarily in order:
A) Go back to 8.1's FF-55 and try letting it use its own libpng, missing
Mozilla's Spectre mitigation. Somewhat higher security risk, given my old
CPU's won't have firmware patches. Stays an 8.1 system.
B) Fall back to FF-52.6ESR, which picks up security mitigations, misses other
fixes, and is somewhat(?) likely to use BLFS-8.1's package versions. This
blazes a new trail, minimal support.
C) Upgrading the system's harfbuzz should require recompiling all the packages it
is a dependency of. Yes, they're using shared libraries, and theoretically one
might be able slip in the upgrade, but the version numbers 1.4.8 --> 1.7.6
suggest enough development that the ABI may have changed. This likely leads to a
wierd hybrid (B)LFS system of uncertain reliability.
D) Let FF-60 use it's own harfbuzz, and whatever comes up next, minimizing
external changes to rustc, hopefully. Gets Mozilla security mitigation and
other fixes, at my most likely point of attack. Browser would be larger, take
more memory if something else, e.g. PDF viewer, also is running, but not
necessarily run slower.
I *really* don't like "C". Harfbuzz-1.7.6 might not like my existing Cairo, and on it goes. Minimizing
collateral change is strongly desired. IF, and only if, "D" & "B" work as described those seem
like worthy of attempting, with "A" being my fallback. None of this answers why the BLFS-8.1 recipe worked for
you developers but wouldn't find my libpng, with my PKG_CONFIG_PATH, etc., shown in my first report.
Have I misinterpretted anything?
E) Rebuild using LFS-dev and BLFS-dev.
Lots of work, but you get a working, up-to-date system.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
