-
Notifications
You must be signed in to change notification settings - Fork 349
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
Support using unversioned lld as linker too #8189
Conversation
On Fedora and RHEL the `lld` executable is the plain unversioned `lld`. That's also usable as a linker if it's recent enough. See dotnet/runtime#58959 (comment) for more details and discussion.
Looks good to me as it is. :) |
I think that checking for lld via clang is a better way. We never execute lld directly, so we really care about the one that clang selects by itself. Especially when you have multiple clang / lld versions installed (like I do). Clang seems to always pick lld of the same version. |
Co-authored-by: Adeel Mujahid <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
If this looks good to everyone, can someone please merge this? I dont have merge powers. |
Thanks! |
On Fedora and RHEL the
lld
executable is the plain unversionedlld
. That's also usable as a linker if it's recent enough.See dotnet/runtime#58959 (comment)
for more details and discussion.
We have been carrying the 6.0 version of this patch for RHEL 8 on arm64 here: https://git.centos.org/rpms/dotnet6.0/blob/c8s/f/SOURCES/runtime-arm64-lld-fix.patch
There was an open question about parsing the lld version using clang like so:
Is that worth implementing?
cc @am11 @crummel @janvorli