Don't assume multiarch locations in Glibc module map #331
Conversation
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
On non-Debian distros, these headers are directly in /usr/include.
|
Could you check if pull request #282 fixes the issue for you? |
|
Oh. Hadn't seen that one :) But I bet it does. It looks like essentially the same thing, only a little better since it parameterizes the locations of the other headers as well. I have to sleep now, but I'll try it out tomorrow. |
|
Seems to do the trick. Closing this one. |
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.
This is the best way I could find to handle the fact that these headers are not in
/usr/include/{arch-triplet}on most distros, but directly in/usr/include. There will probably be a cleaner way to get this path than checking ifCMAKE_LIBRARY_ARCHITECTUREis set when this bug is fixed.