-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node v18+ (and soon v16) has changed to using quictls instead of openssl, nixpkgs derivation is outdated #200515
Comments
To prove my point. With respect to https://gist.github.com/CMCDragonkai/1cac0299230f110a6f842ceb654fa0d0 I downloaded https://nodejs.org/dist/v18.12.1/node-v18.12.1-linux-x64.tar.xz. Then extracted it out with Now using
We have to set the interpreter AND rpath: cd bin
patchelf --set-interpreter '/nix/store/lyl6nysc3i3aqhj6shizjgj0ibnf1pvg-glibc-2.34-210/lib64/ld-linux-x86-64.so.2' ./node
patchelf --set-rpath '/nix/store/lyl6nysc3i3aqhj6shizjgj0ibnf1pvg-glibc-2.34-210/lib:/nix/store/g9x3cm8wdmpm86pyiff6arx8skmdwkn7-gcc-11.3.0-lib/lib' ./node I got the interpreter and rpath from my current Now enter
You can see here that the official Whereas if you get the current
|
Project description
Official nodejs has changed to using quictls (OpenSSL fork with QUIC support). This can be proven by looking at
process.versions
of downloaded nodejs binaries from https://nodejs.org/dist/v18.12.1/node-v18.12.1-linux-x64.tar.xz.However the current nixpkgs derivation for nodejs still uses
openssl
and notquictls
.Nixpkgs does have
quictls
already available https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/libraries/quictls/default.nix.This change is necessary for when NodeJS will have proper quic support.
Older NodeJS versions will still need to use the original openssl.
See the change log here: https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V18.md.
And also nodejs/node#45286 which landed in nodejs/node@4124b03...9fb612e.
This change is also occurring for v16 too: nodejs/node#45274
The text was updated successfully, but these errors were encountered: