From: Andreas Schwab <schwab@linux-m68k.org>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH] Fix glibc 2.34 ABI omission (missing GLIBC_2.34 in dynamic loader)
Date: Wed, 08 Dec 2021 10:56:08 +0100 [thread overview]
Message-ID: <87czm7qv2f.fsf@igel.home> (raw)
In-Reply-To: <87h7bjmnt0.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Wed, 08 Dec 2021 10:46:35 +0100")
On Dez 08 2021, Florian Weimer via Libc-alpha wrote:
> The glibc 2.34 release really should have added a GLIBC_2.34
> symbol to the dynamic loader.
Well, the ship has sailed.
> With it, we could move functions such as dlopen or pthread_key_create
> that work on process-global state into the dynamic loader (once we
> have fixed a longstanding issue with static linking).
Why does this depend on the frozen release?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-12-08 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 9:46 Florian Weimer
2021-12-08 9:56 ` Andreas Schwab [this message]
2021-12-08 10:06 ` Florian Weimer
2021-12-08 10:20 ` Andreas Schwab
2021-12-08 10:28 ` Florian Weimer
2021-12-08 14:06 ` H.J. Lu
2021-12-24 19:01 ` Florian Weimer
2022-01-13 17:22 ` Carlos O'Donell
2022-01-13 17:32 ` Florian Weimer
2021-12-08 16:59 ` Siddhesh Poyarekar
2021-12-13 12:15 ` Florian Weimer
2021-12-13 14:54 ` Siddhesh Poyarekar
2022-01-13 17:56 ` Carlos O'Donell
2022-01-13 18:00 ` Carlos O'Donell
2022-01-22 16:08 ` H.J. Lu
2022-01-24 14:31 ` Florian Weimer
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=87czm7qv2f.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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).