Problem with CppCompilerAndLinker=musl-gcc

[DeafMan1983]

Description

Why does dotnet 10 Preview 7 force to use clang against musl-gcc?

dotnet publish -c Release -r linux-musl-x64 -p:StripSymbols=true -p:CppComilerAndLinker=/usr/bin/musl-gcc  -p:ExtraLinkerArguments="-L/opt/Gtk4Latest/MUSL/l
ib -L/usr/lib/x86_64-linux-musl -I/opt/Gtk4Latest/MUSL/include"
Restore complete (0.7s)
    info NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
  03_SimpleXCB_BASIC_WM failed with 2 error(s) and 1 warning(s) (0.9s) → bin/Release/net10.0/linux-musl-x64/03_SimpleXCB_BASIC_WM.dll
    clang : warning : argument unused during compilation: '-pie' [-Wunused-command-line-argument]
    clang : error : linker command failed with exit code 1 (use -v to see invocation

How do I switch to musl-gcc?

I am working on Ubuntu 24.04.3

Reproduction Steps

I have tried to force to use gcc / musl-gcc

Expected behavior

Why does clang rush again gcc / musl-gcc?

Actual behavior

same like problem with annoying clang jumped

Regression?

No response

Known Workarounds

No response

Configuration

Exe net10.0 _03_SimpleXCB_BASIC_WM enable enable true true link true linux-x64 true

[jkotas]

CppComilerAndLinker

Typo - this should be CppCompilerAndLinker

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

[DeafMan1983]

Thanks for explanation!

But I really don't understand why does it require to load ld-musl-x86_64.so.1?
file tells me:

file ./03_SimpleXCB_BASIC_WM
./03_SimpleXCB_BASIC_WM: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-x86_64.so.1, BuildID[sha1]=e91447618491438a2832d10b7e58d5085c34d562, for GNU/Linux 3.2.0, stripped

ldd tells me:

ldd ./03_SimpleXCB_BASIC_WM
	statically linked

ls -lh tells me:

ls -lh ./03_SimpleXCB_BASIC_WM
-rwxrwxr-x 1 deafman1983 deafman1983 1.6M Sep  3 16:18 ./03_SimpleXCB_BASIC_WM

How do I force to compile against without loading interpreter /lib/ld-musl-x86_64.so.1

I think I need download, compile and install from musl-libc latest version. Is it correctly?

No OpenGL no Vulkan :D, I use CPU-accelerator as software rasterization.

I will work hard on Vulkan Support because xcb has binding with Vulkan.

[jkotas]

How would you do what you are trying to achieve with regular C/C++ compiler? What's the linker command line for that? You need to recreate the same linker command line.

[agocke]

By compiling against musl, are to trying to statically link libc? That would not be done by changing the compiler, you would need to pass different flags to the linker. We don’t currently support static linking since we require dynamically loading OpenSSL. I believe there is some experimental code in the repo to enable that scenario, but you would have to compile from source.

[MichalPetryka]

By compiling against musl, are to trying to statically link libc? That would not be done by changing the compiler, you would need to pass different flags to the linker. We don’t currently support static linking since we require dynamically loading OpenSSL. I believe there is some experimental code in the repo to enable that scenario, but you would have to compile from source.

Static OpenSSL is already supported.

[DeafMan1983]

Thanks for saving me! I have remove all -Wl,-B..... if dotnet gives error of musl-gcc cause --target=x86_64-linux-musl than I copy whole compiler and linker commandline
musl-gcc -static ..... -pie ( end of line )
Than It works fine if I already compile with musl-gcc and it tells me
with file:

file ./03_SimpleXCB_BASIC_WM
./03_SimpleXCB_BASIC_WM: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, with debug_info, not stripped

and ldd:

ldd ./03_SimpleXCB_BASIC_WM
	not a dynamic executable

Wonderful with my app. thanks! I will continue my development and I really understand how do I create it. Than I will port from C# to Rust with x86_64-unknown-linux-musl 💯

Thank you for everything! But I don't need to use openssl. If it is required than I will look it.