nodejs_{18,20}: fix build with LLVM 19#356408
Conversation
a2c4783 to
20a39c1
Compare
|
They both build successfully, although I’d still like to understand the Zlib situation better and hopefully de‐vendor it instead if possible. @aduh95 The V8 patches here might be worth considering for backporting to these Node releases. |
de19624 to
5f909fb
Compare
|
Fixed the rebase mishap. |
44a914d to
c106c88
Compare
ee818d9 to
057709a
Compare
paparodeo
left a comment
There was a problem hiding this comment.
patches look straightforward.
|
@ofborg eval |
|
@aduh95 gentle ping, if you don’t mind taking a look at this :) I feel pretty confident about the V8 backports but would like to understand why the vendored Zlib is getting used at all. |
|
I'm not sure why it's the case, it could be that the vendored one is still compiled without being included in the binary, and I'm not familiar enough with the build tooling to help. |
|
Actually I see that V8 has its own vendored version, separate from the one Node.js uses. I think |
057709a to
f968667
Compare
libc++ 19 no longer supports Clang < 17. This reverts commit b034e4c.
f968667 to
42ef358
Compare
|
Thanks for the insight and review. Perhaps we can devendor it one day, but it can wait. |
First commit cherry‐picked from Randy’s branch. I’ve omitted the return address signing commit as it seems there was upstream churn.
@aduh95 It seems like we try to use shared versions of these libraries? Does that not work on older versions, or not work on Darwin, or something?
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.