On Tue, Nov 10, 2020 at 05:43:00PM +0000, Ken Moffat via blfs-dev wrote: > On Tue, Nov 10, 2020 at 10:43:49AM -0600, Bruce Dubbs via blfs-dev wrote: > > On 11/10/20 6:43 AM, Tim Tassonis via blfs-dev wrote: > > Not directly related to this, but I've had various problems trying > to update nodejs (I only do that if there are vulnerabilities, or if > firefox requires a newer version). The problems seemed to be C++ > version issues - on one system I had to use clang, the version of > g++ (8.something, I think) could not build the latest version of the > same stable series. That might be another candidate for building in > /opt. > For upgrading node.js from what was current when I built 10.0-rc1 it turns out that a newer libuv is needed! I hit this trying to build more recent v14 on my 10.0 system, but alpine hit this when trying to update from 12.18.4 to 12.19.0 : https://gitlab.alpinelinux.org/alpine/aports/-/issues/12028
With current node, using libuv-1.38.1 ftbfs, upgrading to current libuv-1.40.0 lets it build. But as someone posted on that issue: "It’s LTS version of Node.js, so it should contain only backward-compatible changes and mostly fixes." Yeah, right - personally I have a soemwhat low opinion of changes to versions of node :) Maybe next time I fail to update an old system I'll be able to find an error message that soemone has already diagnosed. Weell, I can hope, can't I ? ĸen -- Brave Sir Nigel ran away! When reality reared its ugly head, Sir Nigel turned his tail and fled. Brave brave brave Sir Nigel. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
