Skip to content
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

Fix build against musl libc #318

Merged
merged 1 commit into from
Jan 20, 2022
Merged

Conversation

omajid
Copy link
Member

@omajid omajid commented Jan 18, 2022

Originally reported at dotnet/source-build#2782

Use the same logic as dotnet-isntall.sh to identify whether a system is musl-based or not. For musl-based Linux systems, use linux-musl as the platform name, which leads to better RID names.

Otherwise, we end up trying to use artifacts with an incorrect RID on musl based systems.

In particular, we look for runtime.linux-x64.microsoft.netcore.ildasm which doesn't work on musl-based systems. It's also not produced by source-build builds, which makes building using a previous build of source-build impossible.

cc @ayakael

Originally reported at https://github.com/dotnet/installer/issues/12859

Use the same logic as dotnet-isntall.sh to identify whether a system is
musl-based or not. For musl-based Linux systems, use `linux-musl` as the
platform name, which leads to better RID names.

Otherwise, we end up trying to use artifacts with an incorrect RID on
musl based systems.

In particular, we look for `runtime.linux-x64.microsoft.netcore.ildasm`
which doesn't work on musl-based systems. It's also not produced by
source-build builds, which makes building using a previous build of
source-build impossible.
@omajid omajid requested a review from a team as a code owner January 18, 2022 18:32
@MichaelSimons MichaelSimons requested a review from a team January 20, 2022 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants