From: Alan Modra <amodra@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
GDB <gdb-patches@sourceware.org>,
Binutils <binutils@sourceware.org>, Doug Evans <dje@google.com>
Subject: Re: [PATCH] update automake version to 1.11.6
Date: Mon, 23 Mar 2015 23:46:00 -0000 [thread overview]
Message-ID: <20150323234643.GH26234@bubble.grove.modra.org> (raw)
In-Reply-To: <CAMe9rOroAJN=RP5njJXXZ5BHNRBqpk98VasVLDpfFPRNEPNMYg@mail.gmail.com>
On Mon, Mar 23, 2015 at 05:57:20AM -0700, H.J. Lu wrote:
> We should coordinate this with GCC.
I agree. Using the same version of autotools for binutils+gdb+gcc is
a good idea.
Why are we talking about such a small upgrade though? Wouldn't it
make more sense to move to the latest released autotools? Not for new
features, but for the bug fixes that have accumulated over the years.
I know there have been bug reports about the versions we use..
eg. https://sourceware.org/bugzilla/show_bug.cgi?id=16948
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2015-03-23 23:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150311094134.GE9455@vapier>
2015-03-14 5:30 ` Mike Frysinger
2015-03-19 12:06 ` Joel Brobecker
2015-03-19 22:59 ` Doug Evans
2015-03-19 23:04 ` Mike Frysinger
2015-03-20 23:58 ` Doug Evans
2015-03-21 19:59 ` Mike Frysinger
2015-03-21 21:29 ` Doug Evans
[not found] ` <CAKOQZ8y8aYVM0ncJVfEYBcy1vEUaqLJ+C1un3vC51bpbr=wEfQ@mail.gmail.com>
2015-03-23 12:46 ` Joel Brobecker
2015-03-23 12:57 ` H.J. Lu
2015-03-23 13:13 ` Joel Brobecker
2015-03-23 23:46 ` Alan Modra [this message]
2015-03-24 6:16 ` Mike Frysinger
2015-03-24 17:02 ` Joseph Myers
2015-03-23 20:21 ` Cary Coutant
2015-03-23 20:29 ` H.J. Lu
2015-03-24 6:15 ` Mike Frysinger
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=20150323234643.GH26234@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.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