-
Notifications
You must be signed in to change notification settings - Fork 134
PublishReadyToRun fails with 3.0-preview9 #1232
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
Comments
diag log:
It seems #1231 is also fixing this. I guess |
Waiting to see if #1231 fixes this. |
Still not fixed in 3.0.0 (linux-arm target) |
@gpomykala if you are using Microsoft .NET Core binaries, please report an issue in a different repo, like: https://github.com/dotnet/core. |
It looks like #1231 didn't fix this issue. Any idea what's going on here @nguerrera or @dsplaisted? |
I'm looking at related broken assumption in R2R in 3.1. I'll see if I can figure this out. By any chance can someone provide me with a machine I can SSH to that has the source built dotnet on PATH and ready to test? |
Changing @crummel can you check |
Source-built 3.0 SDK: So the difference from that change is the additional |
Are you sure that it doesn't change to |
Oh, that was dumb. Yeah, confirmed on my CentOS build as well. |
Was the patch applied? |
Oh, I think that's what happened. The 3.0 update PR didn't have your change in it and that's what we tested on, not the merged PR. I'll regenerate a tarball and we'll retest locally, but I'm betting that's all it'll take to fix the issue. |
To be precise it does not work in cross-compilation scenario win-x64->linux-arm. It did work in linux-x64->linux-arm (i learned about that limitation elsewhere) |
@gpomykala there are some limitations, see https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#cross-platformarchitecture-restrictions. |
The new tarball tested out fine and we've tagged the release. |
This works with Microsoft preview9, but not with source-build preview9:
CC @omajid @dagood @crummel
The text was updated successfully, but these errors were encountered: