Fix handling of libtirpc pkg-config files with -L flags#228
Merged
Conversation
Member
|
I'll run this so that it can access AWS. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When querying the libtirpc pkg-config,
TIRPC_LIBSmay return a value that includes a-Lflag which messes up thesedthat's performed here. It could technically return multiple-lflags as well.Example of it breaking:
Instead, we can simplify this by getting rid of the
sedand skipping theAC_CHECK_LIBchecks by simply hardwiring libtirpc to choose the integer functions that all supported libtirpc versions are known to have.