We have an embedded system (Variscite DART-MX8M-MINI) running our own Linux-build based on a kernel from Debian Bullseye (5.4.3-g0267163-dirty SMP PREEMPT aarch64).
.NET Core and the SDK run fine on that system, BUT whenever we start any .NET program (including e.g. dotnet --info) we get the following output at the beginning:
dotnet: /lib64/libstdc++.so.6: no version information available (required by dotnet)
dotnet: /lib64/libstdc++.so.6: no version information available (required by dotnet)
dotnet: /lib64/libstdc++.so.6: no version information available (required by dotnet)
dotnet: /lib64/libstdc++.so.6: no version information available (required by dotnet)
dotnet: /lib64/libstdc++.so.6: no version information available (required by dotnet)
dotnet: /lib64/libstdc++.so.6: no version information available (required by dotnet)
All programs work fine afterwards.
Searching for this error we think this is related to different library-versions in the toolchains (cross-)compiling dotnet and our image.
Is there a way to get rid of these warnings without using the same toolchain (as this is not possible in our case)?
We have an embedded system (Variscite DART-MX8M-MINI) running our own Linux-build based on a kernel from Debian Bullseye (5.4.3-g0267163-dirty SMP PREEMPT aarch64).
.NET Core and the SDK run fine on that system, BUT whenever we start any .NET program (including e.g.
dotnet --info
) we get the following output at the beginning:All programs work fine afterwards.
Searching for this error we think this is related to different library-versions in the toolchains (cross-)compiling
dotnet
and our image.Is there a way to get rid of these warnings without using the same toolchain (as this is not possible in our case)?