public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/14770] [s390] s390 builds fail on binutils < 2.21.52.0.1
Date: Thu, 06 Feb 2014 18:17:00 -0000 [thread overview]
Message-ID: <bug-14770-131-SaEsyOHZxb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14770-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14770
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Host| |s390*-*-*
Summary|s390 builds fail on |[s390] s390 builds fail on
|binutils < 2.21.52.0.1 |binutils < 2.21.52.0.1
--- Comment #5 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
We last increased the required binutils version with:
commit bec039bcefe6a0494a249e2b78e112a0ab60893b
Author: Joseph Myers <joseph@codesourcery.com>
Date: Thu Mar 1 21:23:57 2012 +0000
Require binutils 2.20 or later.
It would probably be reasonable to increase the version (globally, for all
targets) again for glibc 2.20, if you wish to propose a patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-06 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 9:28 [Bug build/14770] New: " siddhesh at redhat dot com
2012-11-16 11:20 ` [Bug build/14770] " aj at suse dot de
2012-11-20 12:20 ` krebbel at linux dot vnet.ibm.com
2012-11-20 12:24 ` krebbel at linux dot vnet.ibm.com
2013-01-09 16:01 ` schwab@linux-m68k.org
2014-02-06 18:17 ` jsm28 at gcc dot gnu.org [this message]
2014-02-25 8:15 ` [Bug build/14770] [s390] " krebbel1 at de dot ibm.com
2014-02-25 15:38 ` krebbel1 at de dot ibm.com
2014-02-25 18:03 ` joseph at codesourcery dot com
2014-04-16 11:06 ` cvs-commit at gcc dot gnu.org
2014-04-16 11:19 ` stli at linux dot vnet.ibm.com
2014-06-14 11:18 ` fweimer at redhat dot com
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=bug-14770-131-SaEsyOHZxb@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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).