From: Joseph Myers <joseph@codesourcery.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/2] Require binutils 2.27 or later to build glibc
Date: Wed, 2 Sep 2020 17:09:37 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.2009021708080.26554@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20200902153726.237493-1-tuliom@linux.ibm.com>
On Wed, 2 Sep 2020, Tulio Magno Quites Machado Filho via Libc-alpha wrote:
> You must use GNU 'binutils' (as and ld) to build the GNU C Library.
> No other assembler or linker has the necessary functionality at the
> moment. As of release time, GNU 'binutils' 2.32 is the newest
> verified to work to build the GNU C Library.
This does not appear to be a regeneration corresponding to the changes in
install.texi.
> diff --git a/NEWS b/NEWS
> index 06e43e0453..60c4fc73ce 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -10,6 +10,9 @@ Version 2.33
> Major new features:
>
>
> +* The minimum GNU Binutils version that can be used to build this version of
> + the GNU C Library is Binutils 2.27.
This belongs under "Changes to build and runtime requirements:", not
"Major new features:".
> You must use GNU @code{binutils} (as and ld) to build @theglibc{}.
> No other assembler or linker has the necessary functionality at the
> -moment. As of release time, GNU @code{binutils} 2.32 is the newest
> +moment. As of release time, GNU @code{binutils} 2.35 is the newest
> verified to work to build @theglibc{}.
Specficically, this install.texi change is not reflected in the INSTALL
changes above.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2020-09-02 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 15:37 Tulio Magno Quites Machado Filho
2020-09-02 15:37 ` [PATCH 2/2] Update INSTALL with package versions that are known to work Tulio Magno Quites Machado Filho
2020-09-02 17:09 ` Joseph Myers [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=alpine.DEB.2.21.2009021708080.26554@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=tuliom@linux.ibm.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).