[Arm Unix build] Fixes for cross building corert tests for arm architectures on Linux#2682
Conversation
|
Hi @sergign60, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution! The agreement was validated by .NET Foundation and real humans are currently evaluating your PR. TTYL, DNFBOT; |
| <OutputType Condition="'$(OutputType)' == ''">Exe</OutputType> | ||
| <OutputPath>$(MSBuildProjectDirectory)\bin\$(Configuration)\</OutputPath> | ||
| <IntermediateOutputPath>$(MSBuildProjectDirectory)\obj\$(Configuration)\</IntermediateOutputPath> | ||
| <OutputPath>$(MSBuildProjectDirectory)\bin\$(Configuration)\$(Variant)\</OutputPath> |
There was a problem hiding this comment.
It is common to call this Platform. Do we have some prior art somewhere where it is called Variant?
It is done here: https://github.com/dotnet/corert/blob/master/src/BuildIntegration/Microsoft.NETCore.Native.Unix.props#L29 |
libjitinterface.so is part of the compiler, so it needs to be built on the host architecture. It is easier to make a simple hello world running first using the cppcodegen option. You may do that first and then work on the RyuJIT one. The RyuJIT one is more involved. |
|
@jkotas many thanks! |
| ) | ||
| ) | ||
|
|
||
| echo msbuild /m /ConsoleLoggerParameters:ForceNoAlign "/p:IlcPath=%CoreRT_ToolchainDir%" "/p:Configuration=%CoreRT_BuildType%" "/p:RepoLocalBuild=true" "/p:FrameworkLibPath=%~dp0\..\bin\Product\%CoreRT_BuildOS%.%CoreRT_BuildArch%.%CoreRT_BuildType%\lib" "/p:FrameworkObjPath=%~dp0\..\bin\obj\Product\%CoreRT_BuildOS%.%CoreRT_BuildArch%.%CoreRT_BuildType%\Framework" !extraArgs! !__SourceFile!.csproj |
|
Now I get the following error: As I understand I need the arm versions of System.Native.a (and libSystem.Globalization.Native.a) Which way can I get them? |
|
@jkotas I take armel versions of System.Native.a from CoreFX and libSystem.Globalizaiton.Native.a from CoreCLR and get the following list of unresolved variables |
|
|
||
| // Allocate non-array object with finalizer. | ||
| // r0 == EEType | ||
| LEAF_ENTRY RhpNewFinalizable, _TEXT |
There was a problem hiding this comment.
It would be nice to make the implementation breakpoint to get nice crash for unimplemented parts once you start running the programs.
|
Thank you! I guess that the next one will have hello world working? |
|
@jkotas |
This pull request contains fixes for the cross building corert tests for arm architectures (arm&armel) on Ubuntu 16.04 x64.
Unfortunately, there are two problems just now:
x64 native variant doesn't create this fail.
any help will be accepted with gratitude