I have a working djbdns compiled against dietlibc, but it is more than 10 years old. I'm trying to compile against musl but the binaries keep coming dynamically linked!
$ cat conf-cc /opt/bin/musl-gcc -static -Os -march=x86-64 -fomit-frame-pointer -pipe -Wall -Wno-trampolines -Wno-maybe-uninitialized -Werror=overflow -mpreferred-stack-boundary=4 -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-unwind-tables -fdata-sections -ffunction-sections -Wl,--gc-sections -fno-asynchronous-unwind-tables -fstrict-aliasing -Wstrict-aliasing=2 -Wno-unused-function -foptimize-sibling-calls -std=c89 -fno-pic -Wl,-z,noseparate-code -fPIE $ cat conf-ld /opt/bin/musl-gcc -s $ file /opt/bin/musl-gcc /opt/bin/musl-gcc: symbolic link to /usr/local/musl/bin/musl-gcc Can someone figure out what's happening? (I have many binaries compiled against musl, and they come out static as intended...) (I know the skarnet server uses djbdns compiled against musl, but is it statically compiled?) Thanks Jorge Almeida
