From: Simon Marchi <simon.marchi@ericsson.com>
To: Joseph Myers <joseph@codesourcery.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
"bkorb@gnu.org" <bkorb@gnu.org>,
"ibuclaw@gdcproject.org" <ibuclaw@gdcproject.org>,
"ian@airs.com" <ian@airs.com>,
"jakub@redhat.com" <jakub@redhat.com>,
"cmtice@google.com" <cmtice@google.com>
Subject: Re: Update GCC to autoconf 2.69, automake 1.15.1
Date: Wed, 31 Oct 2018 14:41:00 -0000 [thread overview]
Message-ID: <55e034c8-8689-dba4-e37b-e7bc9c14add9@ericsson.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1810310322420.32487@digraph.polyomino.org.uk>
On 2018-10-30 11:26 p.m., Joseph Myers wrote:
> This patch (diffs to generated files omitted below) updates GCC to use
> autoconf 2.69 and automake 1.15.1. (That's not the latest automake
> version, but it's the one used by binutils-gdb, with which consistency
> is desirable, and in any case seems a useful incremental update that
> should make a future update to 1.16.1 easier.)
Whenever you feel like bumping gcc to 1.16.1, I can take care of binutils-gdb.
Simon
next prev parent reply other threads:[~2018-10-31 13:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 6:35 Joseph Myers
2018-10-31 8:47 ` Thomas Koenig
2018-10-31 9:14 ` Janne Blomqvist
2018-10-31 10:04 ` Richard Biener
2018-10-31 17:34 ` Joseph Myers
2018-10-31 21:55 ` Ian Lance Taylor
2018-11-01 19:43 ` Janne Blomqvist
2023-05-15 19:07 ` Back to requiring "Perl version 5.6.1 (or later)" [PR82856] (was: Update GCC to autoconf 2.69, automake 1.15.1) Thomas Schwinge
2018-10-31 10:09 ` Update GCC to autoconf 2.69, automake 1.15.1 Richard Biener
2018-10-31 14:36 ` Ian Lance Taylor
2018-10-31 14:41 ` Simon Marchi [this message]
2018-10-31 17:40 ` Joseph Myers
2018-10-31 17:22 ` Eric Gallager
2018-10-31 18:39 ` Joseph Myers
2018-12-03 3:39 ` Iain Buclaw
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=55e034c8-8689-dba4-e37b-e7bc9c14add9@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=bkorb@gnu.org \
--cc=cmtice@google.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.com \
--cc=ibuclaw@gdcproject.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libstdc++@gcc.gnu.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).