Skip to content

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.
@MichaelSimons MichaelSimons merged commit 220fc35 into dotnet:release/6.0 Jan 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants