Fix FreeBSD linking by simplifying libjose.map #173
Merged
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
…pose and are capturing the environ and __prognam symbols from libc on FreeBSD causing various linking errors due to those symbols being erroneously not exported. Minor change in meson.build to look for build_machine vs. host_machine because the linking is happening on the build machine and thus the linker syntax is build machine dependent.
Collaborator
|
@sergio-correia : PTAL |
sergio-correia
approved these changes
Jul 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Remove the locals regexes from libjose.map. They seem to serve no purpose and are capturing the environ and __prognam symbols from libc on FreeBSD causing various linking errors due to those symbols being erroneously not exported. Minor change in meson.build to look for build_machine vs. host_machine because the linking is happening on the build machine and thus the linker syntax is build machine dependent.
This should correct #152