On 6/3/20 4:56 PM, Wayne Blaszczyk via blfs-dev wrote:
On Wed, 2020-06-03 at 12:57 +0100, Ken Moffat via blfs-dev wrote:
I started writing this in the ticket for node-v12.18.0 (#13628),
but the C++ scope errors when using system nghttp2 prompted me to go
with 12.18.0 for the moment.  And then I discovered that the same
FTBFS occurred in 12.18.0, but right at the end of the build instead
of very early on. <sigh/>

I'm fairly sure we have stuck to v12 at my suggestion, based on
https://nodejs.org/en/about/releases/ (v12 is 'active' until 20th
October, v14 is now 'current' i.e. development).  However, python2
has had its last release and I keep hoping that browsers
(specifically firefox and falkon via qtwebengine) will eventually
no-longer require it.  Node v12 will always require python2, but
python3 was added in v13 (which is now EOL) and is preferred if
found.


I've been building nodejs 12 for quite some time without python2 with the 
following patches.

https://github.com/nodejs/node/commit/be926c7e21ddf0e24e26b7a74aabda66e91a9da5.patch
https://github.com/nodejs/node/commit/b2ccbb27dc98dfd771d7d5592e139e2001baa56c.patch
https://github.com/nodejs/node/commit/3a076bae9c256a830353cf47170599d30baa6c1b.patch

Thanks Wayne. We may be able to use these, but it really does not do a lot of good if the only two packages we have (FF and TB) that use nodejs also require python2.

Will continue to investigate.

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

Reply via email to