From: Joseph Myers <joseph@codesourcery.com>
To: Alan Modra <amodra@gmail.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
Simon Marchi <simon.marchi@ericsson.com>,
<gdb-patches@sourceware.org>, <binutils@sourceware.org>
Subject: Re: Update autotools version for gdb and binutils
Date: Tue, 08 May 2018 22:12:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1805082209240.32321@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20180508023041.GV28782@bubble.grove.modra.org>
On Tue, 8 May 2018, Alan Modra wrote:
> I wasn't saying you must change all of binutils-gdb, let alone gcc,
> just that it would be nice. binutils-gdb config/* is copied from gcc
And as it's the start of development for GCC 9, it's essentially the
optimal time for such a risky change in GCC.
It's libtool for which an update may be the riskiest (necessary to revert
libtool commit 3334f7ed5851ef1e96b052f2984c4acdbf39e20c, see
<https://gcc.gnu.org/ml/gcc-patches/2011-01/msg00520.html>, and need to
check for any local changes relative to the last libtool version merged
from that aren't in the new libtool version used). I don't know whether
updating other tools in GCC would require updating libtool or whether the
updates can be independent.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-05-08 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 18:44 [PATCH] gdb: Update autotools version used for gnulib import Simon Marchi
2018-05-04 19:34 ` Simon Marchi
2018-05-07 6:15 ` Alan Modra
2018-05-07 14:28 ` Simon Marchi
2018-05-08 2:30 ` Update autotools version for gdb and binutils Alan Modra
2018-05-08 20:39 ` Matt Rice
2018-05-08 22:12 ` Joseph Myers [this message]
2018-05-09 15:46 ` Simon Marchi
2018-05-10 14:40 ` Alan Modra
2018-06-15 0:49 ` Simon Marchi
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.20.1805082209240.32321@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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