From: Andreas Schwab <schwab@suse.de>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org, Zack Weinberg <zack@owlfolio.org>,
daniel.fellows@arm.com
Subject: Re: [PATCH v2 2/2] crypt: Remove libcrypt support
Date: Tue, 16 Jan 2024 13:21:56 +0100 [thread overview]
Message-ID: <mvm5xztii3f.fsf@suse.de> (raw)
In-Reply-To: <ZaZv6tsKhNAsUu3S@arm.com> (Szabolcs Nagy's message of "Tue, 16 Jan 2024 12:00:42 +0000")
On Jan 16 2024, Szabolcs Nagy wrote:
> fyi, this means that if you copy new glibc over an old system
> the old libcrypt.so.1 will stop working because of missing
> __snprintf@GLIBC_PRIVATE symbol.
>
> e.g. this breaks some of our native glibc test setups, unless
> we carefully rebuild a libcrypt to be compatible with both the
> new glibc and the native system (old systems don't have compat
> libxcrypt packaged).
I don't think there is any guarantee for GLIBC_PRIVATE symbols to stay
around, and mixing related libraries from different versions of glibc
isn't supported either.
So you would have to build libxcrypt for your old system to replace its
libcrypt.so.1 if you want to use the new glibc there.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2024-01-16 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 12:11 [PATCH v2 0/2] " Adhemerval Zanella
2023-10-02 12:11 ` [PATCH v2 1/2] sparc: Remove optimize md5, sha256, and sha512 Adhemerval Zanella
2023-10-30 12:52 ` Carlos O'Donell
2023-10-30 13:04 ` Carlos O'Donell
2023-10-02 12:11 ` [PATCH v2 2/2] crypt: Remove libcrypt support Adhemerval Zanella
2023-10-02 14:21 ` Zack Weinberg
2023-10-30 12:52 ` Carlos O'Donell
2023-10-31 13:43 ` Joseph Myers
2023-10-31 14:00 ` Adhemerval Zanella Netto
2024-01-16 12:00 ` Szabolcs Nagy
2024-01-16 12:21 ` Andreas Schwab [this message]
2023-10-30 12:52 ` [PATCH v2 0/2] " Carlos O'Donell
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=mvm5xztii3f.fsf@suse.de \
--to=schwab@suse.de \
--cc=adhemerval.zanella@linaro.org \
--cc=daniel.fellows@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.com \
--cc=zack@owlfolio.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).