-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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.Js does not build successfully using --shared-openssl configure flag #35213
Comments
Here's a snippet of the compiler output:
|
Your copy of openssl is incompatible - probably too old. Seeing it's missing Closing, not a bug. |
I'm pretty sure I am using OpenSSL 1.1.1 -- here's the output from
... is there some more precise way to identify? |
Also:
|
You need a newer (or more complete) version of OpenSSL 1.1.1. In general it's best to match the version of OpenSSL bundled with whichever version/branch of node you're compiling for. Node v14.x currently ships with OpenSSL 1.1.1g for example. A quick search reveals that a bugfix for |
Is it possible/reasonable to consider this a bug in nodejs' configure logic (not reporting the version dependency)? |
No. Building against shared libraries is effectively not a supported configuration. We allow it because it's something distro vendors want/need but with the understanding that they're on the hook when it breaks, not us. |
That's reasonable, thanks! FWIW, I am not a distro-vendor, and being able to dynamically link OpenSSL is useful to me because I was running into a bug linking node w/ another binary that also has OpenSSL linked. (Only adding this color in case it influences future decisions to abandoned the shared-lib configuration support. |
@mscdex could I ask: how does one know what version of OpenSSL node is bundled with? I'm running into the same issue with Ubuntu 18.04 using the certified OpenSSL libraries (1.1.1) and I'm trying to build node against this library already on my system.
|
@D4V3M0NK You should be able to consult https://nodejs.org/dist/index.json or https://nodejs.org/dist/index.tab to get technical information about each release, including the OpenSSL version that is ordinarily bundled with node. |
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
100%
What is the expected behavior?
Building with --shared-openssl should succeed, yield a node.exe or node.dll (when building with --shared, as in my case) which links against an external openssl dll.
What do you see instead?
The build fails.
Additional information
I have tried this with all of the tags mentioned above, as well as the master branch from github without success.
The text was updated successfully, but these errors were encountered: