RFC: how to document musl-crypt failure ?
Sam James
sam@gentoo.org
Mon Nov 9 11:24:10 GMT 2026
Andreas Schwab <schwab@suse.de> writes:
> On Nov 09 2026, Alejandro Colomar wrote:
>
>> I've CCed Rich and also musl and glibc, since they probably want to
>> comment. I've also CCd shadow-utils.
>
> libcrypt is no longer part of glibc, it is now provided by libxcrypt.
Indeed. But while we're here..
For libxcypt, it's determined by the configure option:
--disable-error-tokens. By default, error tokens are enabled.
I've switched Gentoo to use --disable-*. Fedora already did many years
ago so package failures should be smoked out by now:
* https://src.fedoraproject.org/rpms/libxcrypt/c/853ed305cd53c67bb2827dce78b889c8d187e1e0?branch=rawhide
* https://bugzilla.redhat.com/show_bug.cgi?id=1611784
Debian uses the libxcrypt default. I didn't check other distros yet.
sam
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 418 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20261109/40eb2cc4/attachment.sig>
More information about the Libc-alpha
mailing list