[FR] providing linux musl target

[bb-Ricardo]

I had trouble running yozf on not so current linux OSs and it would give me following error messages for the unknown-linux-gnu target

./yozf-x86_64-unknown-linux-gnu-0.0.18: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by ./yozf-x86_64-unknown-linux-gnu-0.0.18)
./yozf-x86_64-unknown-linux-gnu-0.0.18: /lib64/libc.so.6: version `GLIBC_2.39' not found (required by ./yozf-x86_64-unknown-linux-gnu-0.0.18)

It would be great if a musl build could also be provided.

Thank you

[Mcdostone]

Hi,

I gave a try to build yozefu with the musl libc but i don't know if it's possible yet according the number of issues.

I don't think I will have time to work on this because it is very time-consuming to debug compilation errors.
Any PR is welcomed though. I keep this issue opened for tracking.

If you need to run Yozefu in a small pod, I recommand you to take a look at Wolfi or a distroless image.

[bb-Ricardo]

Hi,

yes you are right. I remember that there was an issue with rdkafka and musl.

[bb-Ricardo]

I had a look and it seems to work with the musl-cross compiler suite:

docker run --rm -ti -v $(pwd):/build rust:1-slim-trixie /bin/bash
apt-get update && apt-get install --no-install-recommends -y git build-essential cmake libclang-dev curl clang
mkdir -p /opt/x-tools
curl -L https://github.com/cross-tools/musl-cross/releases/download/20250929/x86_64-unknown-linux-musl.tar.xz | tar -xJf - -C /opt/x-tools 

export PATH="/opt/x-tools/x86_64-unknown-linux-musl/bin:$PATH"

cd /build

cat <<EOF >> .cargo/config.toml
[env]
CARGO_TARGET_X86_64_UNKNOWN_LINUX_MUSL_LINKER = "x86_64-unknown-linux-musl-gcc"
CC_x86_64_unknown_linux_musl="x86_64-unknown-linux-musl-gcc"
CXX_x86_64_unknown_linux_musl="x86_64-unknown-linux-musl-g++"
AR_x86_64_unknown_linux_musl="x86_64-unknown-linux-musl-ar"
RANLIB_x86_64_unknown_linux_musl="x86_64-unknown-linux-musl-ranlib"
STRIP_x86_64_unknown_linux_musl = "x86_64-unknown-linux-musl-strip"
EOF

rustup target add x86_64-unknown-linux-musl

cargo build --target x86_64-unknown-linux-musl
cargo build --release --target x86_64-unknown-linux-musl

But I failed to compile it with --features gssapi-vendored,libz-static,ssl-vendored as it always throws errors for krb5-src. Also for target x86_64-unknown-linux-gnu.

[Mcdostone]

Nice work!
In this case, what we can do is to disable gssapi-vendored when we build for x86_64-unknown-linux-musl since gssapi depends on krb5-src .

[bb-Ricardo]

Hi,

I'm not sure if it is a good idea to release binaries for different targets with adifferent set of enabled features.

As a user I would find this very confusing. On the other hand it could be a note in each release description of what features are build in and which ones are missing.

The next rust version 1.93.0 bumps linux musl for all x86_64 targets to 1.25 as well: https://blog.rust-lang.org/2025/12/05/Updating-musl-1.2.5/

Maybe it's worth trying out rust nightly and if that works out of the box just wait for the release of 1.93.0

And I just noticed that krb5-src is archived since Nov 17th 2025: https://github.com/MaterializeInc/rust-krb5-src

What do you think?

[Mcdostone]

Today, it's already the case: For instance, windows binaries don't have the gssapi-vendored,libz-static features enabled since I'm facing issues compiling on Windows. If you use the SASL feature on Windows, I think Yozefu panics.

I agree it's confusing but there is no better solution so far. I'll add a new section in the documentation to know which features are enabled for each target.

We can try rust 1.93.0 but I doubt it will work. Do you have time to try it?