Starting with #Rust 1.62.0, tests for gettext-rs crate segfault on x86_64-unknown-linux-musl because pthread_mutex_lock is missing from the binary. I failed to figure out why: github.com/Koka/gettext-rs/iss If you're into this sort of thing, please lend me a hand!

#Rustlang

@L29Ah Technically the segfault is in GNU gettext, which is a C library :P But it happens because (I think) Rust doesn't link the entirety of pthreads into the binary. Overall it looks like the Rust crate relied on symbols that compiler used for its own stuff, and now that the compiler no longer uses those symbols and doesn't include them in the binary, the crate is broken.

But I can't figure out how to ask Rust to pull that symbols for me :(

@L29Ah Um, yes? GNU software can call POSIX interfaces just fine. (Sorry I don't have a funny response for you here.)

Follow

@minoru @L29Ah "Rust is full featured and can do anything!"

@L29Ah Rust has one too: crates.io/crates/gettext But if you're building an application in multiple languages (e.g. C and Rust), then it's slightly easier to use a single gettext implementation in both languages; that's where gettext-sys and gettext-rs come in.

@nm0i

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.