-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Can't go from build to wasm testing in one go on a M1 Mac #72722
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescription
However, runtime/src/mono/nuget/Microsoft.NET.Workload.Mono.Toolchain.Manifest/WorkloadManifest.json.in Lines 356 to 365 in 555a791
Since I am building in arm64 environment, only packages for arm64 exist, and wasm-tools try to install packages for x64 and it fails. Reproduction Steps
Expected behaviorWe can install Actual behaviorWhen dotnet install
Regression?No response Known Workarounds
runtime/src/mono/nuget/Microsoft.NET.Workload.Mono.Toolchain.Manifest/WorkloadManifest.json.in Line 363 in 555a791
However, we felt that incorporating this change would affect many users since it was not published on nuget. ConfigurationNo response Other informationIs ref?: #71622 (comment)
|
I believe this works fine now, please reopen if not |
Description
build-all
task, used when building undersrc/mono/wasm
, can generate the necessary packages to install thewasm-tools
workload.The generated packages are OS and architecture dependent, e.g., on M1 Mac,
Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.browser-wasm.7.0.0-dev.nupkg
is generated.However,
wasm-tools
dependencyMicrosoft.NETCore.App.Runtime.AOT.Cross.browser-wasm
specifiesMicrosoft.NETCore.App.Runtime.AOT.osx-x64.Cross.browser-wasm
as the alias of the dependency.runtime/src/mono/nuget/Microsoft.NET.Workload.Mono.Toolchain.Manifest/WorkloadManifest.json.in
Lines 356 to 365 in 555a791
Since I am building in arm64 environment, only packages for arm64 exist, and wasm-tools try to install packages for x64 and it fails.
Reproduction Steps
Expected behavior
We can install
wasm-tools
that for testing on M1 MacActual behavior
When dotnet install
Microsoft.NETCore.App.Runtime.AOT.Cross.browser-wasm
, it fali.Regression?
No response
Known Workarounds
Microsoft.NETCore.App.Runtime.AOT.osx-arm64.Cross.browser-wasm
runtime/src/mono/nuget/Microsoft.NET.Workload.Mono.Toolchain.Manifest/WorkloadManifest.json.in
Line 363 in 555a791
However, we felt that incorporating this change would affect many users since it was not published on nuget.
Configuration
No response
Other information
Is
osx-arm64
support like M1 Mac within the scope of .NET 7?Please let me know if you have an issue that can be tracked.
ref?: #71622 (comment)
The text was updated successfully, but these errors were encountered: