From: Andreas Schwab <schwab@linux-m68k.org>
To: Sam James <sam@cmpct.info>
Cc: Fangrui Song <maskray@google.com>,
Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Should we make DT_HASH dynamic section for glibc?
Date: Sat, 01 Oct 2022 10:41:06 +0200 [thread overview]
Message-ID: <87edvsx7fh.fsf@linux-m68k.org> (raw)
In-Reply-To: <FCD1A9C7-933E-4A51-96DB-46D889A3D032@cmpct.info> (Sam James's message of "Sat, 1 Oct 2022 09:31:27 +0100")
On Okt 01 2022, Sam James wrote:
> True, but it helps those who have been on the fence and didn't
> want to deviate from glibc upstream. It also shows that it's
> an acceptable move to make.
It's much easier to configure binutils with
--enable-default-hash-style=both.
--
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:[~2022-10-01 8:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:31 Adhemerval Zanella Netto
2022-08-08 20:40 ` Carlos O'Donell
2022-08-08 20:56 ` Carlos O'Donell
2022-08-08 22:59 ` Fangrui Song
2022-08-08 23:36 ` Sam James
2022-08-09 9:21 ` Florian Weimer
2022-09-30 12:56 ` Carlos O'Donell
2022-10-01 7:40 ` Fangrui Song
2022-10-01 8:31 ` Sam James
2022-10-01 8:41 ` Andreas Schwab [this message]
2022-10-01 13:49 ` Florian Weimer
2022-10-03 20:57 ` Michael Hudson-Doyle
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=87edvsx7fh.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=maskray@google.com \
--cc=sam@cmpct.info \
/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).