Building with target x86_64-unknown-linux-musl

[claudius108]

Hi!

Thanks for this nice crate! It works fine.

I would like to build it with target x86_64-unknown-linux-musl, but I got some errors. How anyone managed to build it as such?

Thanks,
Claudius

[dginev]

I suspect you're the first! Would you like to share the error?

Maybe there is some configuration issue that can be addressed generically. The sibling crate rust-libxml has had a few extra contributions, can you build that one successfully already?

[claudius108]

Thank you for your answer, Deyan! The error message is below. The build is in a GitLab job, with the image rust:latest. My aim is to have a static binary to run XSLT stylesheets. I will test with rust-libxml. CT error: failed to run custom build command for `libxml v0.3.3` Caused by: process didn't exit successfully: `/builds/adwmainz/nfdi4culture/cdmd/xml-utils/./target/release/build/libxml-3a9a3f64b3b1a812/build-script-build` (exit status: 101) --- stdout cargo:rerun-if-env-changed=LIBXML_2.0_NO_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG_ALLOW_CROSS_x86_64-unknown-linux-musl cargo:rerun-if-env-changed=PKG_CONFIG_ALLOW_CROSS_x86_64_unknown_linux_musl cargo:rerun-if-env-changed=TARGET_PKG_CONFIG_ALLOW_CROSS cargo:rerun-if-env-changed=PKG_CONFIG_ALLOW_CROSS cargo:rerun-if-env-changed=PKG_CONFIG_x86_64-unknown-linux-musl cargo:rerun-if-env-changed=PKG_CONFIG_x86_64_unknown_linux_musl cargo:rerun-if-env-changed=TARGET_PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-musl cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_musl cargo:rerun-if-env-changed=TARGET_PKG_CONFIG_SYSROOT_DIR cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR --- stderr thread 'main' panicked at /usr/local/cargo/registry/src/index.crates.io-1949cf8c6b5b557f/libxml-0.3.3/build.rs:38 :5: Could not find libxml2. note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

…

On Fri, 7 Mar 2025 at 16:36, Deyan Ginev ***@***.***> wrote: I suspect you're the first! Would you like to share the error? Maybe there is some configuration issue that can be addressed generically. The sibling crate rust-libxml <https://github.com/KWARC/rust-libxml/> has had a few extra contributions, can you build that one successfully already? — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANKHHWGRWG7QSENBUSNSDT2TGVHDAVCNFSM6AAAAABYRKTBBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBWGYYDONBSGY> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: dginev]*dginev* left a comment (KWARC/rust-libxslt#5) <#5 (comment)> I suspect you're the first! Would you like to share the error? Maybe there is some configuration issue that can be addressed generically. The sibling crate rust-libxml <https://github.com/KWARC/rust-libxml/> has had a few extra contributions, can you build that one successfully already? — Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANKHHWGRWG7QSENBUSNSDT2TGVHDAVCNFSM6AAAAABYRKTBBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBWGYYDONBSGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Cu stimă, Claudius Teodorescu