-
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
deps: exclude linker scripts for windows builds #42973
Conversation
Just wondering how ignoring those files adds the provider? There are so many files updated it's hard to tell from the PR itself. |
This PR is not about adding a provider. The first commit the actual content of the changes in this PR and then we need to regenerate the OpenSSL header files. |
This commit ignore fips.ld and legacy.ld linker scripts for Windows environments. Fixes: nodejs#40854
752d5bb
to
4eb4d0e
Compare
@mhdawson I've taken a closer look at this and my understanding is that the linker scripts are not used with |
@danbev ok thanks for the update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR-URL: #42973 Reviewed-By: Michael Dawson <midawson@redhat.com>
PR-URL: #42973 Reviewed-By: Michael Dawson <midawson@redhat.com>
This commit ignore fips.ld and legacy.ld linker scripts for Windows environments. PR-URL: nodejs#42973 Fixes: nodejs#40854 Reviewed-By: Michael Dawson <midawson@redhat.com>
PR-URL: nodejs#42973 Reviewed-By: Michael Dawson <midawson@redhat.com>
@danbev is this able to be landed in v16.x or is there a backport PR for this? It didn't land cleanly in v16.x-staging for the v16.15.2 release. |
This commit ignore fips.ld and legacy.ld linker scripts for Windows
environments using msbuild.
Fixes: #40854