Skip to content

Warn when we map unrecognized library files to -l flags. #14746

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

Merged
merged 1 commit into from
Jul 23, 2021

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Jul 23, 2021

This is a rather an odd feature and I think we should notify users if they
are relying on it. Honestly I doubt many are.

See #14689 for an example of how confusing it can be when it goes wrong.

Also, make sure we strip off the full suffix in the case of .so.1.2.3
suffixes.

@sbc100 sbc100 requested a review from kripken July 23, 2021 22:18
@sbc100 sbc100 force-pushed the warn_on_library_mapping branch from 51a2f70 to 123375a Compare July 23, 2021 22:18
Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense.

lgtm with a test for the new warning.

This is rather an odd feature and I think we should notify users if they
are relying on it.  Honestly I doubt many are.

See #14689 for an example of how confusing it can be when it goes wrong.

Also, make sure we strip off the full suffix in the case of `.so.1.2.3`
suffixes.
@sbc100 sbc100 force-pushed the warn_on_library_mapping branch from 123375a to 3969a9a Compare July 23, 2021 22:40
@sbc100 sbc100 enabled auto-merge (squash) July 23, 2021 22:41
@sbc100 sbc100 merged commit add60e9 into main Jul 23, 2021
@sbc100 sbc100 deleted the warn_on_library_mapping branch July 23, 2021 23:36
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 this pull request may close these issues.

2 participants