|
From: | Daniel Gerber |
Subject: | bug#34526: Updating node.js |
Date: | Thu, 21 Feb 2019 18:02:36 +0100 |
Hi, 2019-02-20, Jelle Licht:
Daniel Gerber <address@hidden> writes:[snip] What about statically linking llhttp's C "sources" included in node? Building v11.10.0 succeeds with this:You could do this, of course, but afaics this is not acceptable forinclusion in Guix proper.I don't really see any way forward between convincing the fine node folks to see the 'error of their ways', or to implement a ABI-compatiblereplacement for llhttp that we can actually bootstrap.
Although I would prefer the convincing-the-fine-node-folks solution, here are two more ways to avoid dropping node with the EOL of 8.x(LTS) at the end of 2019.
- Remove llhttp and keep only the "legacy" http-parser, or- Accept to bootstrap it -- I mean use intermediary self-compiling steps, like ccl, golang, java, or haskell do. The build-time dependencies are: address@hidden -> llhttp -> ts-node -> typescript -> self (typescript), plus quite a few npm packages. It seems that address@hidden or 9.x should be a native-input to later versions, but I do not know enough of Guile / Guix packaging to do it myself anytime soon.
[Prev in Thread] | Current Thread | [Next in Thread] |