Open ellahathaway opened 4 months ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
Is this a duplicate of https://github.com/dotnet/source-build/issues/2932?
Is this a duplicate of https://github.com/dotnet/source-build/issues/2932?
It's similar/has the same end goal. I think the difference is that as of the creation of the current issue, we have the ability to "technically" build source-build with a portable RID/portable build property set, but the build itself is not actually portable due to bugs. Not sure if that was possible when Rich created the other issue?
See https://github.com/dotnet/installer/pull/15163#issuecomment-1873396096 for a fix that Nix folks used.
Based on https://github.com/dotnet/sdk/pull/40843, it's clear that while the VMR is configured to be portable, source build does not work in a portable state due to bugs.
For example, while certain OSs build successfully with PortableBuild=true (centos9 for example), the produced SDK does not work. An example is the following run of the scenario tests with a source-build SDK that was built using the PortableBuild=true property:
Another example of source-build being portable build incompatible is the fact that aspnetcore fails to build on alpine:
In the above error message, aspnetcore fails to build because it is looking for the linux-x64 version of crossgen. Earlier, this package was built and outputted as
Microsoft.NETCore.App.Crossgen2.linux-musl-x64
. See https://github.com/dotnet/sdk/pull/40843#issuecomment-2125740662