-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Provide symlink for musl-gcc
?
#16
Comments
I am not sure we should assume x86_64 like that. Is there a convention around it, @richfelker? |
I don't think it's a good idea for scripts to assume |
In that sense though doesn't it do the same thing that |
Semantically, |
Fair enough, it sounds like these scripts might get confused if they can't then run the binaries they compiled, and users might want to target different architectures at that point. We'll let them explicitly symlink |
@FiloSottile I almost gave up on trying to compile to
Now I can finally use I'd suggest to copy your previous comment in the README of this repository, because it seems like really important to know for ppl which just want to make things work quickly. Thank you |
Many scripts expect the command
musl-gcc
to exist. Making a symlink in my$PATH
frommusl-gcc
to$(which x86_64-linux-musl-gcc)
caused scripts that have this expectation to work. Seems like it'd be useful to provide this by default?The text was updated successfully, but these errors were encountered: