From: Nick Clifton <nickc@redhat.com>
To: Fangrui Song <i@maskray.me>
Cc: binutils@sourceware.org
Subject: Re: The 2.38 branch has been created.
Date: Wed, 9 Feb 2022 15:50:20 +0000 [thread overview]
Message-ID: <1aa739be-5690-93a0-eaff-b3f69b1886d1@redhat.com> (raw)
In-Reply-To: <MWHPR1201MB0110C2AE8A32FAF1A45EFEE4CB2E9@MWHPR1201MB0110.namprd12.prod.outlook.com>
Hi Fangrui,
> Hi Nick, I'd hope that the 2.38 branch has a proper way specifying
> output section type...
> https://sourceware.org/pipermail/binutils/2022-February/119600.html
> which may possibly be used by Fedora.
Sorry - that feature was too new to get into the 2.38 release.
But... Fedora rawhide binutils only uses the 2.38 release as a starting
point. So it is entirely possible that output section type patch can
be added on. Just ask the Fedora binutils maintainer. Oh, wait, that
is me. It would help me if you could file a Fedora bugzilla for adding
this feature as that way I can keep track of it.
Cheers
Nick
next prev parent reply other threads:[~2022-02-09 15:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 12:58 Nick Clifton
2022-01-23 13:15 ` H.J. Lu
2022-01-23 13:32 ` [PATCH] Regenerate configure files with autoconf 2.69 H.J. Lu
2022-01-24 14:59 ` The 2.38 branch has been created Nick Clifton
2022-01-25 12:39 ` Matthias Klose
2022-01-25 15:37 ` Nick Clifton
2022-01-29 5:29 ` Alan Modra
2022-01-30 13:32 ` Matthias Klose
2022-01-30 13:53 ` H.J. Lu
2022-01-30 13:58 ` Matthias Klose
2022-01-30 22:48 ` Alan Modra
2022-01-25 17:22 ` Szabolcs Nagy
2022-01-27 10:18 ` Szabolcs Nagy
2022-01-30 15:02 ` H.J. Lu
2022-02-08 2:07 ` Palmer Dabbelt
2022-02-08 15:43 ` Nick Clifton
2022-02-09 9:21 ` Fangrui Song
[not found] ` <MWHPR1201MB0110C2AE8A32FAF1A45EFEE4CB2E9@MWHPR1201MB0110.namprd12.prod.outlook.com>
2022-02-09 15:50 ` Nick Clifton [this message]
2022-02-10 4:53 ` Fangrui Song
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=1aa739be-5690-93a0-eaff-b3f69b1886d1@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=i@maskray.me \
/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).