Skip to content
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

Noisy warning in configure: WARNING: No acceptable ld.gold linker found! #35872

Closed
MylesBorins opened this issue Oct 29, 2020 · 2 comments
Closed

Comments

@MylesBorins
Copy link
Contributor

$ ./configure
Node.js configure: Found Python 3.8.6...
WARNING: No acceptable ld.gold linker found!
WARNING: warnings were emitted in the configure phase
INFO: configure completed successfully

It seems like this is related to the inclusion of using the ld.gold linker as part of --use-section-ordering-file.

The default compiler setup on OSX does not have these features... further, I don't believe the default configuration for node.js even uses --use-section-ordering-file. When I saw this warning at first I was worried that there had been some sort of regression in my build tools locally (something that can happen with OSX / Xcode upgrades) and I lots about an hour of time trying to debug things.

In the end I really couldn't find an easy way to get the ld.gold linker installed on OSX at all.

With all this in mind I wonder if it might make sense for us to only present the warning if the flag that requires the ld.gold linker is passed.

/cc @gabrielf whom I believe added this feature

@MylesBorins
Copy link
Contributor Author

pinging @gabrielschulhof (pinged wrong gabriel the first time sorry

@joyeecheung
Copy link
Member

I also think that we should only warn about this when --use-section-ordering-file is set

MylesBorins added a commit to MylesBorins/node that referenced this issue Nov 6, 2020
Currently warning is printed called even if the selection ordering flag
has not been passed.

Only print warning if `--limit-configure-section-file`
has been passed to configure.

Fixes: nodejs#35872
danielleadams pushed a commit that referenced this issue Nov 9, 2020
Currently warning is printed called even if the selection ordering flag
has not been passed.

Only print warning if `--limit-configure-section-file`
has been passed to configure.

Fixes: #35872

PR-URL: #35955
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
BethGriggs pushed a commit that referenced this issue Dec 9, 2020
Currently warning is printed called even if the selection ordering flag
has not been passed.

Only print warning if `--limit-configure-section-file`
has been passed to configure.

Fixes: #35872

PR-URL: #35955
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
BethGriggs pushed a commit that referenced this issue Dec 10, 2020
Currently warning is printed called even if the selection ordering flag
has not been passed.

Only print warning if `--limit-configure-section-file`
has been passed to configure.

Fixes: #35872

PR-URL: #35955
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
BethGriggs pushed a commit that referenced this issue Dec 15, 2020
Currently warning is printed called even if the selection ordering flag
has not been passed.

Only print warning if `--limit-configure-section-file`
has been passed to configure.

Fixes: #35872

PR-URL: #35955
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants