From: Alan Modra <amodra@gmail.com>
To: Tom Kacvinsky <tkacvins@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: .relr.dyn, binutils 2.37 and glibc 2.36
Date: Tue, 13 Sep 2022 17:35:42 +0930 [thread overview]
Message-ID: <YyA51srKJo801M3r@squeak.grove.modra.org> (raw)
In-Reply-To: <CAG_eJLeMJ9FT9tLoNBj9vyz2dgs4vFt5Qn2igS9hZtyYaKZnCg@mail.gmail.com>
On Mon, Sep 12, 2022 at 02:27:24PM -0400, Tom Kacvinsky via Binutils wrote:
> I have seen lots of stuff float by on the glibc and binutils list about
> changes to each related to relocations. My I've lost track of what
> changes have been made. I am not sure if this should be posted to
> the glibc list or here, so I am trying here first instead of cross posting.
>
> I have a colleague that is using a glibc 2.36 based system and is
> using binutils 2.37 (one that I built from source, not the system ld).
>
> This is the error he gets
>
> /opt/binutils-2.37/bin/ld: /lib64/libc.so.6: unknown type [0x13] section
> `.relr.dyn'
For a very long time ld.bfd has rejected object files with unknown
ELF sections. Quite possibly it would be better if ld.bfd accepted
dynamic objects with unknown section types, but that's the way it
works now.
> But then he follows up that while ld.bfd doesn't work, ld.gold (i.e.,
> -fuse-ld=gold)
> does work.
>
> My recollection is that the changes made in the newer versions of glibc for
> relocations required a newer binutils (2.38, I think).
Yes.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2022-09-13 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 18:27 Tom Kacvinsky
2022-09-12 18:55 ` Andreas Schwab
2022-09-13 8:05 ` Alan Modra [this message]
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=YyA51srKJo801M3r@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=tkacvins@gmail.com \
/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).