-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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 v17.1.0 does not build with --shared-openssl #40783
Comments
If I configure node without |
We see this when building with |
This is linked with #40958 and now also affects 16.13.1. |
This appears to be fixed in the TOT of the master branch. |
For reference, this was fixed in 5f348b4. |
Will it be backported to 16.x given it regressed in 16.13.1? |
Yes, eventually. General policy is for changes to have been in a current release for two weeks before backporting to LTS: https://github.com/nodejs/Release#lts-staging-branches |
Sounds good, thanks! |
Version
v17.1.0
Platform
Darwin hostname 16.7.0 Darwin Kernel Version 16.7.0: Tue Jan 30 11:27:06 PST 2018; root:xnu-3789.73.11~1/RELEASE_X86_64 x86_64
Subsystem
No response
What steps will reproduce the bug?
./configure --ninja --with-intl=system-icu --without-dtrace --without-npm --shared-openssl --shared-zlib
make
How often does it reproduce? Is there a required condition?
100%
What is the expected behavior?
I expected node to build.
What do you see instead?
Additional information
I think that the problem is that it should not be trying to build openssl when configured with --shared-openssl. I hacked the build.ninja to not include openssl in the build dependencies, and it built correctly.
Regression:
Version v17.0.1 built correctly.
The text was updated successfully, but these errors were encountered: