-
Notifications
You must be signed in to change notification settings - Fork 544
Support compiler prefix x86_64-linux-musl
#1443
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 compiler prefix x86_64-linux-musl
#1443
Conversation
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.
Thanks, this seems to make sense, although if musl-gcc is a fallback to x86_64-linux-musl-gcc in all situations, I'd prefer to not do fallback, and only attempt to use x86_64-linux-musl-gcc (just like we do for the similar aarch64-linux-musl-gcc).
I kept the inclusion of the |
|
My issue with that is that it seems wrong still? E.g. if cross-compiling from |
Yeah, that's fair. In the latest commit, it only uses the |
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.
Excellent, thanks!
Will be released next Friday.
Motivation
Context
I found that in some (most?) environments, the musl compiler to use for targeting
x86_64-unknown-linux-muslis prefixed withx86_64-linux-musl. For example, on Ubuntu (AMD64) themusl-devpackage contains/usr/bin/x86_64-linux-musl-gccbut it does not contain/usr/bin/musl-gcc, which is provided by themusl-toolspackage. (Themusl-toolspackage depend onmusl-dev.)When
musl-toolsis installed,/usr/bin/musl-gccis simply a symlink to the former:Change
This adds another compiler prefix (
x86_64-linux-musl) to check for when building for this target.