From: Xi Ruoyao <xry111@xry111.site>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Carlos O'Donell <carlos@redhat.com>,
libc-alpha <libc-alpha@sourceware.org>
Cc: binutils@sourceware.org, caiyinyu <caiyinyu@loongson.cn>,
Wang Xuerui <i@xen0n.name>, liuzhensong <liuzhensong@loongson.cn>
Subject: Re: glibc 2.36 - Slushy freeze (3 weeks to release)
Date: Tue, 12 Jul 2022 09:02:48 +0800 [thread overview]
Message-ID: <24dc4b2df07e2b5ddf3a42077383c386dbba019c.camel@xry111.site> (raw)
In-Reply-To: <d08a21a6a3b6f58bc9b99a0526b2ef53400e55be.camel@xry111.site>
On Tue, 2022-07-12 at 08:48 +0800, Xi Ruoyao via Libc-alpha wrote:
> > So do we need a binutils 2.39 to have a workable glibc build or is the
> > 2.38 suffice?
>
> We need a 2.39, or backport one change [1] to 2.38.
>
> [1]: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=3b14682a
P. S. this change is not only needed to build glibc, but also needed to
build anything with GCC. That's why I said "completely unusable".
Maybe "completely" is too strong: 2.38 is functional with this change
backported.
And yes, it's already backported into binutils-2.38 branch [2]. But we
didn't get a new 2.38.1 release containing it :(.
[2]: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=d54081c6
(To be fair: a plain binutils-2.38 release also does not work fine for
x86 and we had to backport changes [3][4] too.)
[3]: https://wiki.linuxfromscratch.org/lfs/ticket/5011
[4]: https://wiki.linuxfromscratch.org/lfs/ticket/5012
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-07-12 1:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fef8c3c7-fd30-d8b5-e539-f0f21d562c51@redhat.com>
2022-07-11 16:06 ` Xi Ruoyao
2022-07-11 19:10 ` Adhemerval Zanella Netto
2022-07-12 0:48 ` Xi Ruoyao
2022-07-12 1:02 ` Xi Ruoyao [this message]
2022-07-12 2:32 ` Alan Modra
2022-07-12 4:24 ` Fangrui Song
2022-07-12 6:19 ` Jan Beulich
2022-07-12 6:42 ` WANG Xuerui
2022-07-12 7:33 ` Florian Weimer
2022-07-12 8:49 ` Xi Ruoyao
2022-07-12 8:58 ` Florian Weimer
2022-07-12 9:24 ` Xi Ruoyao
2022-07-12 10:21 ` Adhemerval Zanella Netto
2022-07-12 11:01 ` Adhemerval Zanella Netto
2022-07-12 12:15 ` Michael Matz
2022-07-12 13:17 ` Florian Weimer
2022-07-12 13:28 ` Michael Matz
2022-07-15 22:34 ` Hans-Peter Nilsson
2022-07-12 12:48 ` caiyinyu
2022-07-12 13:00 ` Xi Ruoyao
2022-07-12 7:33 ` Andrew Waterman
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=24dc4b2df07e2b5ddf3a42077383c386dbba019c.camel@xry111.site \
--to=xry111@xry111.site \
--cc=adhemerval.zanella@linaro.org \
--cc=binutils@sourceware.org \
--cc=caiyinyu@loongson.cn \
--cc=carlos@redhat.com \
--cc=i@xen0n.name \
--cc=libc-alpha@sourceware.org \
--cc=liuzhensong@loongson.cn \
/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).