From: Sam James <sam@gentoo.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Alejandro Colomar <alx+linux-man@kernel.org>,
Walter Harms <wharms@bfs.de>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
Rich Felker <dalias@libc.org>,
libc-alpha@sourceware.org, musl@lists.openwall.com,
~hallyn/shadow@lists.sr.ht
Subject: Re: RFC: how to document musl-crypt failure ?
Date: Mon, 09 Nov 2026 11:24:10 +0000 [thread overview]
Message-ID: <87zevii6xx.fsf@gentoo.org> (raw)
In-Reply-To: <mvmqzgugv6q.fsf@suse.de>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 418 bytes --]
next prev parent reply other threads:[~2026-11-09 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 8:59 RFC: how to document musl-crypt failure ? Walter Harms
2026-11-09 10:10 ` Alejandro Colomar
2026-11-09 10:23 ` Andreas Schwab
2026-11-09 11:24 ` Sam James [this message]
2026-11-09 13:56 ` [musl] " Rich Felker
2026-11-09 15:50 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zevii6xx.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=alx+linux-man@kernel.org \
--cc=dalias@libc.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=musl@lists.openwall.com \
--cc=schwab@suse.de \
--cc=wharms@bfs.de \
--cc=~hallyn/shadow@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox