NativeAOT + classlib + macOS host + linux-bionic-arm64 target: doesn't work out of the box / inscrutable errors #101727
Comments
dotnet-policy-service
bot
added
the
untriaged
|
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
Context: dotnet/runtime#101727 Previously, trying to use `dotnet publish` from a macOS host would result in obscure build failures, e.g. % dotnet publish -c Release … clang : error : invalid linker name in argument '-fuse-ld=lld' Apply the workaround from dotnet/runtime#101727 to workaround this. The `$(ANDROID_NDK_HOME)` environment variable requuired: # we're all xamarin-android devs here, right? ;-) % export ANDROID_NDK_HOME=$HOME/android-toolchain/ndk % dotnet publish -c Release # Creates DotNet/bin/Release/net8.0/linux-bionic-arm64/publish/libdotnet.so
|
Related: attempting to follow the NativeAOT+Bionic instructions at https://github.com/dotnet/runtime/blob/017593d90781d797df8b2241f6d1f83c236c442b/src/coreclr/nativeaot/docs/android-bionic.md from macOS + x64 results in similar errors described above: Results in the errors:
|
Context: dotnet/runtime#101727 Previously, trying to use `dotnet publish` from a macOS host would result in obscure build failures, e.g. % dotnet publish -c Release … clang : error : invalid linker name in argument '-fuse-ld=lld' Apply the workaround from dotnet/runtime#101727 to workaround this. The `$(ANDROID_NDK_HOME)` environment variable requuired: # we're all xamarin-android devs here, right? ;-) % export ANDROID_NDK_HOME=$HOME/android-toolchain/ndk % dotnet publish -c Release # Creates DotNet/bin/Release/net8.0/linux-bionic-arm64/publish/libdotnet.so * Set `$ANDROID_NDK_HOME` from `devcontainer.json` Co-authored-by: Jonathan Peppers <jonathan.peppers@microsoft.com>
|
(Speaking of reading comprehension…) android-bionic.md has a Known issues section section, which has a much better & simpler fix: <ItemGroup Condition="$(RuntimeIdentifier.StartsWith('linux-bionic'))">
<LinkerArg Include="-Wl,--undefined-version" />
</ItemGroup> |
|
I've updated the original report to take my previous comment into consideration. |
What's your build logging verbosity? I believe the error message you're seeing comes from this line, since that's the line that precedes the objcopy checks: clang potentially erroring out is expected and handled, the logic just wants to know if it will fail. The output is logged with |
"Default"; no verbosity specified. All commands were specified in the original comment: % dotnet new classlib -n HelloBionicSharedLib
% cd HelloBionicSharedLib
% dotnet publish -c Release -r linux-bionic-arm64 -p:PublishAotUsingRuntimePack=true -p:PublishAot=true
Attached.
That's not quite true; this line: sets The "offending" Additionally, it contains the string "error", which means that the default "error warning format" will detect this as an error. Locally, if I set # with local patch to add IgnoreStandardErrorWarningFormat=true:
% dotnet publish -c Release -r linux-bionic-arm64 -p:PublishAotUsingRuntimePack=true -p:PublishAot=true
MSBuild version 17.9.8+b34f75857 for .NET
Determining projects to restore...
All projects are up-to-date for restore.
HelloBionicSharedLib -> /private/tmp/HelloBionicSharedLib/bin/Release/net8.0/linux-bionic-arm64/HelloBionicSharedLib.dll
clang: error: invalid linker name in argument '-fuse-ld=lld'
/Users/jon/.nuget/packages/microsoft.dotnet.ilcompiler/8.0.4/build/Microsoft.NETCore.Native.Unix.targets(236,5): error : Symbol stripping tool ('llvm-objcopy' or 'objcopy') not found in PATH. Try installing appropriate package for llvm-objcopy or objcopy to resolve the problem or set the StripSymbols property to false to disable symbol stripping. [/private/tmp/HelloBionicSharedLib/HelloBionicSharedLib.csproj]If the idea is to entirely remove diff --git a/src/coreclr/nativeaot/BuildIntegration/Microsoft.NETCore.Native.Unix.targets b/src/coreclr/nativeaot/BuildIntegration/Microsoft.NETCore.Native.Unix.targets
index 7441f7da0f6..575caae39ae 100644
--- a/src/coreclr/nativeaot/BuildIntegration/Microsoft.NETCore.Native.Unix.targets
+++ b/src/coreclr/nativeaot/BuildIntegration/Microsoft.NETCore.Native.Unix.targets
@@ -285,7 +285,7 @@ The .NET Foundation licenses this file to you under the MIT license.
<Error Condition="'$(_WhereLinker)' != '0' and '$(CppCompilerAndLinkerAlternative)' == '' and '$(_IsApplePlatform)' != 'true'"
Text="Requested linker ('$(CppLinker)') not found in PATH." />
- <Exec Command=""$(CppLinker)" -fuse-ld=lld -Wl,--version" Condition="'$(LinkerFlavor)' == 'lld'" IgnoreExitCode="true" StandardOutputImportance="Low" ConsoleToMSBuild="true">
+ <Exec Command=""$(CppLinker)" -fuse-ld=lld -Wl,--version" Condition="'$(LinkerFlavor)' == 'lld'" IgnoreExitCode="true" StandardOutputImportance="Low" StandardErrorImportance="Low" IgnoreStandardErrorWarningFormat="true" ConsoleToMSBuild="true">
<Output TaskParameter="ExitCode" PropertyName="_LinkerVersionStringExitCode" />
<Output TaskParameter="ConsoleOutput" PropertyName="_LinkerVersionString" />
</Exec> |
|
Thank you! The binlog confirms that it comes from that line. The patch in your comment looks good to me - would you mind submitting a PR with it? I can do it myself, but I thought that since you already did the work, I shouldn't steal your credit. |
|
@MichalStrehovsky: PR filed as: #102000 |
It was later corrected #92272 (comment) and afterwards the whole thing was removed in #100755. The docs suggest this workaround for .NET 8 https://github.com/dotnet/runtime/blob/0fb0188a137f3d53a2ebd719d7a684327938609a/src/coreclr/nativeaot/docs/android-bionic.md#known-issues |
|
The current problem is that the PR #102000 attempts to improve its behavior. |
|
I'm closing as this is expected based on our documentation: we do not support cross-os publishing with Native AOT. https://learn.microsoft.com/en-us/dotnet/core/deploying/native-aot/cross-compile has the information. |
dotnet-policy-service
bot
removed
the
untriaged
dotnet-policy-service
bot
added
the
in-pr
Description
Trying to use NativeAOT to build a linux-bionic-arm64 shared library from macOS does not work out of the box.
Reproduction Steps
Expected behavior
Above
dotnet publishshould produce a.sofile.Actual behavior
Yes, neither
llvm-objcopynorobjcopyare in$PATH, but the first line "hides" the second;invalid linker name in argument '-fuse-ld=lld'looks like the "root" error, and doesn't really make sense by itself.The second line is actually explanatory, if you get past reading the first. (Yes, reading comprehension is hard. Regardless, error messages should be actionable, and the first line is not actionable.)
If we fix that up:
…then it still fails to build:
#92272 (comment) suggests adding the following snippet to the
.csproj:This doesn't work because the
$(RuntimeIdentifier)comparison is wrong, but if we fix that:…then it still fails to build:
Regression?
No.
Known Workarounds
A cause of the original
ld.lld : error : version script assignment of 'V1.0' to symbol '_init' failed: symbol not definedis that none of the.afiles used in the link command provide that symbol. Perhaps one of them should?In the meantime,
android-bionic.mdhas a Known issues section which suggests adding a-Wl,--undefined-versionlinker argument.Update
HelloBionicSharedLib.csprojto end with:then add
HelloBionicSharedLib.targetsto theHelloBionicSharedLibdirectory with contents:and the
dotnet publishcommand now succeeds without error, producing abin/Release/net8.0/linux-bionic-arm64/publish/HelloBionicSharedLib.soartifact.Configuration
.NET Configuration:
I have no idea if it's specific to this configuration.
Other information
No response
The text was updated successfully, but these errors were encountered: