-
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
[release/8.0] Wrong architecture libc++ bundled with wasm cross-compilers on linux-arm64 #93015
Comments
OK, this is specifically an issue for Wasm, the linux-arm64->android-* has the correct arch libc++ |
Not specific to release/8.0, bad in main |
The combination of https://github.com/dotnet/runtime/blame/main/src/mono/mono.proj#L258 and https://github.com/dotnet/runtime/blame/main/src/mono/mono.proj#L991 is clearly always wrong for WASM, and whoever wrote these conditionals is an idiot. Working on a fix ASAP. |
browser-wasm cross-compilers, due to incorrect assumption that the build architecture should be used for wasm cases. Closes: dotnet#93015
…wasm cross-compilers, due to incorrect assumption that the build architecture should be used for wasm cases. Closes: #93015
…rowser-wasm cross-compiler (#93070) * Try to resolve x64 libc++ being included with linux-arm64 to browser-wasm cross-compilers, due to incorrect assumption that the build architecture should be used for wasm cases. Closes: #93015 * Still bad. Remove a condition. --------- Co-authored-by: Jo Shields <joshield@microsoft.com> Co-authored-by: Jo Shields <directhex@apebox.org>
Description
x64 libc++ is getting bundled. Investigating why.
Reproduction Steps
Expected behavior
Actual behavior
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: