Unbreak build with Clang #25
Open
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
Only Gold and LLD implement --no-gnu-unique but Makefile is too primitive to figure out which toolchain is used by default.
Merged
|
the issue is that without no gnu unique reloading (unloading, then loading) a plugin does not work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Only Gold and LLD support
--no-gnu-unique. GCC defaults to-fuse-ld=bfd, so--no-gnu-uniqueis discarded unless GCC itself was built with--disable-gnu-unique-object. Clang doesn't have such magic, so--no-gnu-uniquefails because it's not supported by the compiler unlike-Wl,--no-gnu-uniquewhich is passed to the linker and works fine with-fuse-ld=gold,-fuse-ld=lldor when/usr/bin/ldis Gold/LLD.Also, Meson support in
hyprbarsdoesn't try to pass--no-gnu-unique