This is just a heads up for anyone using firefox.

The firefox-78.0esr release should be available on Monday, meanwhile
I've been building what I hope is the last release candidate on my
systems.

The obvious big gotcha for 78.0 is the need to update to
rustc-1.42.0.  If you are not using currnet llvm, that means
building rustc-1.42.0 with its shipped llvm - I think I've covered
that adequately in the wiki entry for rustc (using system llvm with
old llvm used to build, but failed its tests catastrophically).

However, the real problem is node-js.  For 78.0 the minimum required
version is 10.19.0.  In BLFS-9.0 and earlier we had older versions,
and those worked with the firefox-68esr series.

For BLFS-9.0 and BLFS-8.4 I have now managed to build node-v10.21.0
using CC=clang CXX=clang++ with CFLAGS="$CFLAGS -std=c11" and
CXXFLAGS="$CXXFLAGS -std=c++14".  On 9.0, firefox-78.0esr has built,
on 8.4 firefox is still building.

However, on BLFS-8.3 I have not managed to compile a suitable
version of node-js.  My intention was to stop updating 8.3 from
July (2 years after the release, plus time for users to actually
build the release), so arguably my 8.3 system has expired slightly
earlier than planned.

With 8.3, clang failed with undefined variable erorrs.  I then tried
gcc, that told me that deduced return type need c++14 or gnu++14.
So I tried gcc with c++14, but rthat failed with c++ scope errors
(which was the original problem with node-v12.).

I think that firefox-68esr will be updated to .10, and then to .11
and 12 after another 4 weeks and 8 weeks.  if anyone is using
firefox on a system with such an old toolchain, I suggest that you
stick with 68esr and prepare to upgrade the whole system to
something newer.

ĸen
-- 
       He died at the console, of hunger and thirst.
       Next day he was buried, face-down, nine-edge first.
                              - the perfect programmer
-- 
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