[release/6.0] Fix build against musl libc #319
Merged
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.
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