[NativeAOT] cross-compiling to osx-arm64 from osx-x64 does not work

[jkotas]

Reported by @lemonmojo in #73678 (comment):

I'm also running into the same error using .NET 8 Preview 1.

While cross-compiling to x64 from an M1 machine works fine for me, I can't get the reverse (cross-compiling to ARM64 from an Intel machine) to work.

I'm not using any packages in this project. In fact, the issue is very easy to reproduce:

dotnet new classlib -n "AOTTest"
cd AOTTest
dotnet publish -p "PublishAot=true" -r osx-x64
dotnet publish -p "PublishAot=true" -r osx-arm64

Publishing using dotnet publish -r osx-x64 and dotnet publish -r osx-arm64 works fine from an M1 machine.
While on an Intel machine only the x64 build works and the ARM64 one fails with the error message:

/Users/redacted/.nuget/packages/microsoft.dotnet.ilcompiler/8.0.0-preview.1.23110.8/build/Microsoft.NETCore.Native.Publish.targets(74,5): error : The PrivateSdkAssemblies ItemGroup is required for _ComputeAssembliesToCompileToNative [/Path/to/Project.csproj].

So here's what works and what doesn't work in my testing:
ARM64 -> x64: OK
ARM64 -> ARM64: OK
x64 -> x64: OK
x64 -> ARM64: Error

[jkotas]

@filipnavara Do you happen to know what the problem is?

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Reported by @lemonmojo in #73678 (comment):

I'm also running into the same error using .NET 8 Preview 1.

While cross-compiling to x64 from an M1 machine works fine for me, I can't get the reverse (cross-compiling to ARM64 from an Intel machine) to work.

I'm not using any packages in this project. In fact, the issue is very easy to reproduce:

dotnet new classlib -n "AOTTest"
cd AOTTest
dotnet publish -p "PublishAot=true" -r osx-x64
dotnet publish -p "PublishAot=true" -r osx-arm64

Publishing using dotnet publish -r osx-x64 and dotnet publish -r osx-arm64 works fine from an M1 machine.
While on an Intel machine only the x64 build works and the ARM64 one fails with the error message:

/Users/redacted/.nuget/packages/microsoft.dotnet.ilcompiler/8.0.0-preview.1.23110.8/build/Microsoft.NETCore.Native.Publish.targets(74,5): error : The PrivateSdkAssemblies ItemGroup is required for _ComputeAssembliesToCompileToNative [/Path/to/Project.csproj].

So here's what works and what doesn't work in my testing:
ARM64 -> x64: OK
ARM64 -> ARM64: OK
x64 -> x64: OK
x64 -> ARM64: Error

Author:	jkotas
Assignees:	-
Labels:	untriaged, area-NativeAOT-coreclr
Milestone:	-

[am11]

While cross-compiling to x64 from an M1 machine works fine for me, I can't get the reverse (cross-compiling to ARM64 from an Intel machine) to work.

FWIW, the CI is cross-compiling for arm64 on osx-x64 machine.

[filipnavara]

It used to work, and this error is new to me. I'll try to reproduce it on my machine, but just in case that doesn't work, it would be useful to get a MSBuild binlog. It can be produced with a /bl switch on the dotnet publish command line, which will produce a msbuild.binlog file.

[kant2002]

I do have binlog from @lemonmojo and we troubleshoot that issue in #coreclr channel on dotnet evolution.
Issue was that runtime package was not downloaded as part of restore(?) process.
We solve that by manually adding package <PackageReference Include="runtime.osx-arm64.Microsoft.DotNet.ILCompiler" Version="8.0.0-preview.1.23110.8" />.
Discrepancies in differences quite possible was because ARM64 -> x64: OK was first attemp, and ARM64 machine has runtime package in the cache already.

[jkotas]

If you do not use explicit Microsoft.DotNet.ILCompiler package reference, it should just work.

The explicit runtime.osx-arm64.Microsoft.DotNet.ILCompiler package reference should be only needed if you use explicit Microsoft.DotNet.ILCompiler package reference. This is documented in https://github.com/dotnet/runtime/blob/main/src/coreclr/nativeaot/docs/compiling.md#cross-architecture-compilation.

[filipnavara]

It reproduces. The RuntimePackagePath property in ImportRuntimeIlcPackageTarget gets set to an empty value.

[kant2002]

I ask OP manually add this to download package in the cache. I think after this package in the Nuget cache issue will disappear.

[kant2002]

It obviosly still a bug, but I do not troubleshoot that far and I do not have Mac