-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
mac: deps/openssl compiled, even with --shared-openssl
#40958
Comments
targos
added
build
Issues and PRs related to build files or the CI.
openssl
Issues and PRs related to the OpenSSL dependency.
labels
Nov 25, 2021
FWIW, this patch did fix the mac builds. I've submitted it as #40965 but feel free to close if it should be the more complicated fix to ensure the tests are built with the shared openssl, which I don't know how to do. |
This has now regressed in 16.13.1 as well. |
mhdawson
added a commit
to mhdawson/io.js
that referenced
this issue
Feb 4, 2022
Fixes: nodejs#41633 Fixes: nodejs#40958 - move test-crypto-engine so that dummy engine is only built if tests are run Signed-off-by: Michael Dawson <mdawson@devrus.com>
bengl
pushed a commit
to bengl/node
that referenced
this issue
Feb 21, 2022
Fixes: nodejs#41633 Fixes: nodejs#40958 - move test-crypto-engine so that dummy engine is only built if tests are run Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: nodejs#41830 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com>
bengl
pushed a commit
to bengl/node
that referenced
this issue
Feb 21, 2022
Fixes: nodejs#41633 Fixes: nodejs#40958 - move test-crypto-engine so that dummy engine is only built if tests are run Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: nodejs#41830 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com>
danielleadams
pushed a commit
to danielleadams/node
that referenced
this issue
Apr 21, 2022
Fixes: nodejs#41633 Fixes: nodejs#40958 - move test-crypto-engine so that dummy engine is only built if tests are run Signed-off-by: Michael Dawson <mdawson@devrus.com> PR-URL: nodejs#41830 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Darshan Sen <raisinten@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Richard Lau <rlau@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
17.1.0
Platform
Darwin hostname 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64
Subsystem
node.gyp
What steps will reproduce the bug?
build with
though I believe only
--shared-openssl
is relevant.How often does it reproduce? Is there a required condition?
on anny mac build with
--shared-openssl
, as far as I can tell.What is the expected behavior?
deps/openssl
is not compiled when--shared-openssl
is given.What do you see instead?
deps/openssl
is compiled (and fails!). This should just be wasted build time, compiling openssl that isn't going to be used, but the fact that it happens to fail means it's blocking progress. I don't know if the build failure is relevant, but the fact is it shouldn't be built at all (and isn't on linux with the same input)Additional information
I believe it is caused by test_crypto_engine (added in #40481) depending on
deps/openssl/openssl.gyp:openssl
whenOS=="mac" and node_use_openssl=="true"
.The simplest patch is to change the condition to
node_use_openssl=="true" and node_shared_openssl=="false"
because the content appears to assume thatdeps/openssl
is used, but I'm not sure if the test should still be built with shared openssl. If so, it should at least properly link/include shared openssl, instead ofdeps/openssl
. That, I don't know how to patch. The linux builds succeed, but the fact that it unconditionally includes fromdeps/openssl/include
suggests it might do something wrong, depending on the version of the shared openssl.This is seen updating nodejs on conda-forge:
The text was updated successfully, but these errors were encountered: