Working around LibGitSharp2 not working on arm64? #3723
Comments
omajid
changed the title
|
The version comes from here: I'd kind of expect that to come from Arcade, so the best solution might be to remove that and use an Arcade default... but maybe doing a one-time upgrade is fine as a fix for this particular problem? |
omajid
referenced
this issue
in omajid/dotnet-core-setup
Aug 13, 2019
To enable building core-setup on arm64 (hosted, not cross compiled), we
need to do a few things:
- Set the right TargetArchitecture
Use the currently running architecture to decide whether to default to
x64 or to switch to arm64 when TargetArchitecture is not specified
- Use the right coreclr JIT
If we are cross-compiling, we need to use the x86_arm64 libclrjit.so.
But if we are building on an arm64 host, we need filter the list of
found libclrjit.so files to pick the normal-RID (eg, linux-arm64)
libclrjit.so from the two:
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/5.0.0-alpha1.19403.2/runtimes/linux-arm64/native/libclrjit.so
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/5.0.0-alpha1.19403.2/runtimes/x64_arm64/native/libclrjit.so
This commit does not fix the issue where sourcelink is broken on arm64
and so the build fails because of missing information about sources. See
https://github.com/dotnet/core-setup/issues/7653 for more information
about that.
omajid
referenced
this issue
in omajid/dotnet-core-setup
Aug 13, 2019
To enable building core-setup on arm64 (hosted, not cross compiled), we
need to do a few things:
- Set the right TargetArchitecture
Use the currently running architecture to decide whether to default to
x64 or to switch to arm64 when TargetArchitecture is not specified
- Use the right coreclr JIT
If we are cross-compiling, we need to use the x86_arm64 libclrjit.so.
But if we are building on an arm64 host, we need to filter the list of
found libclrjit.so files to pick the normal-RID (eg, linux-arm64)
libclrjit.so from the two:
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/linux-arm64/native/libclrjit.so
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/x64_arm64/native/libclrjit.so
- Use a version of SourceLink that supports arm64
We need to upgrade SourceLink to a version that contains
dotnet/sourcelink#288. This commit just
updates it to the latest version.
Fixes #7653
omajid
referenced
this issue
in omajid/dotnet-core-setup
Aug 13, 2019
To enable building core-setup on arm64 (hosted, not cross compiled), we
need to do a few things:
- Set the right TargetArchitecture
Use the currently running architecture to decide whether to default to
x64 or to switch to arm64 when TargetArchitecture is not specified
- Use the right coreclr JIT
If we are cross-compiling, we need to use the x86_arm64 libclrjit.so.
But if we are building on an arm64 host, we need to filter the list of
found libclrjit.so files to pick the normal-RID (eg, linux-arm64)
libclrjit.so from the two:
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/linux-arm64/native/libclrjit.so
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/x64_arm64/native/libclrjit.so
- Use a version of SourceLink that supports arm64
We need to upgrade SourceLink to a version that contains
dotnet/sourcelink#288. This commit just
updates it to the latest version.
Fixes #7653
omajid
referenced
this issue
in omajid/dotnet-core-setup
Aug 13, 2019
To enable building core-setup on arm64 (hosted, not cross compiled), we
need to do a few things:
- Set the right TargetArchitecture
Use the currently running architecture to decide whether to default to
x64 or to switch to arm64 when TargetArchitecture is not specified
- Use the right coreclr JIT
If we are cross-compiling, we need to use the x86_arm64 libclrjit.so.
But if we are building on an arm64 host, we need to filter the list of
found libclrjit.so files to pick the normal-RID (eg, linux-arm64)
libclrjit.so from the two:
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/linux-arm64/native/libclrjit.so
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/x64_arm64/native/libclrjit.so
- Use a version of SourceLink that supports arm64
We need to upgrade SourceLink to a version that contains
dotnet/sourcelink#288. This commit just
updates it to the latest version.
Fixes #7653
omajid
referenced
this issue
in omajid/dotnet-core-setup
Aug 13, 2019
To enable building core-setup on arm64 (hosted, not cross compiled), we
need to do a few things:
- Set the right TargetArchitecture
Use the currently running architecture to decide whether to default to
x64 or to switch to arm64 when TargetArchitecture is not specified
- Use the right coreclr JIT
If we are cross-compiling, we need to use the x86_arm64 libclrjit.so.
But if we are building on an arm64 host, we need to filter the list of
found libclrjit.so files to pick the normal-RID (eg, linux-arm64)
libclrjit.so from the two:
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/linux-arm64/native/libclrjit.so
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/x64_arm64/native/libclrjit.so
- Use a version of SourceLink that supports arm64
We need to upgrade SourceLink to a version that contains
dotnet/sourcelink#288. This commit just
updates it to the latest version.
Fixes #7653
omajid
referenced
this issue
in omajid/dotnet-core-setup
Aug 14, 2019
To enable building core-setup on arm64 (hosted, not cross compiled), we
need to do a few things:
- Set the right TargetArchitecture
Use the currently running architecture to decide the HostArch. Use that
as the default value of TargetArchitecture, unless another value was
provided by the build configuration.
- Use the right coreclr JIT
If we are cross-compiling, we need to use the x86_arm64 libclrjit.so.
But if we are building on an arm64 host, we need to pick the normal-RID
(eg, linux-arm64) libclrjit.so from the two:
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/linux-arm64/native/libclrjit.so
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/x64_arm64/native/libclrjit.so
- Use a version of SourceLink that supports arm64
We need to upgrade SourceLink to a version that contains
dotnet/sourcelink#288. This commit just
updates it to the latest version.
Fixes #7653
dagood
referenced
this issue
in dotnet/core-setup
Aug 15, 2019
To enable building core-setup on arm64 (hosted, not cross compiled), we
need to do a few things:
- Set the right TargetArchitecture
Use the currently running architecture to decide the HostArch. Use that
as the default value of TargetArchitecture, unless another value was
provided by the build configuration.
- Use the right coreclr JIT
If we are cross-compiling, we need to use the x86_arm64 libclrjit.so.
But if we are building on an arm64 host, we need to pick the normal-RID
(eg, linux-arm64) libclrjit.so from the two:
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/linux-arm64/native/libclrjit.so
./.packages/transport.runtime.linux-arm64.microsoft.netcore.jit/###/runtimes/x64_arm64/native/libclrjit.so
- Use a version of SourceLink that supports arm64
We need to upgrade SourceLink to a version that contains
dotnet/sourcelink#288. This commit just
updates it to the latest version.
Fixes #7653
|
Hi, How to support MIPS64 bootstrap? There are MIPS64 EA SDKs: https://github.com/gsvm/loongson-dotnet/releases Thanks, |
|
Workaround for MIPS64: Cheers, |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am trying to build core-setup (commit
e4c55203) on arm64.Aside from a number of other issues,
./build.shgives me this error:I know there are multiple fixes (some in the works) to get this working on arm64:
Can someone help me get one of these fixes to be consumed by core-setup?
The text was updated successfully, but these errors were encountered: