Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
	gdb-patches@sourceware.org, binutils@sourceware.org
Cc: Simon Marchi <simon.marchi@ericsson.com>
Subject: Re: [PATCH 1/2] Bump to autoconf 2.69 and automake 1.15.1
Date: Fri, 15 Jun 2018 14:22:00 -0000	[thread overview]
Message-ID: <df0ee0e1-8e97-ffb6-edb2-c0aee39b262f@redhat.com> (raw)
In-Reply-To: <20180615004309.29913-1-simon.marchi@polymtl.ca>

Hi Simon,

> And to avoid requiring multiple
> builds of autoconf/automake, it was suggested that we bump the required
> version of those tools for all binutils-gdb.

Thanks very much for taking on this task.

You do not appear to have updated the AC_PREREQ macro statements in the
various */configure.ac files.  Is this intentional ?

Also the config/override.m4 file still contains a hard coded requirement 
for autoconf 2.64 exactly.

The patch did not include renamed *.texinfo files, although that was
simple enough to fix.

Otherwise so far, my testing has been showing no signs of any real problems.

Cheers
  Nick


  parent reply	other threads:[~2018-06-15 14:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15  0:43 Simon Marchi
2018-06-15  0:46 ` [PATCH 2/2] Generated files Simon Marchi
2018-06-15  3:00   ` Simon Marchi
2018-06-15 14:22 ` Nick Clifton [this message]
2018-06-15 14:38   ` [PATCH 1/2] Bump to autoconf 2.69 and automake 1.15.1 Simon Marchi
2018-06-15 14:58     ` Nick Clifton
2018-06-15 15:14       ` Simon Marchi
2018-06-15 15:30         ` Nick Clifton
2018-06-15 15:38           ` Simon Marchi
2018-06-15 15:54             ` Nick Clifton
2018-06-16  1:39   ` Alan Modra
2018-06-16  3:56     ` Simon Marchi
2018-06-16  7:17       ` Andreas Schwab
2018-06-18  2:46       ` Alan Modra
2018-06-18  3:05         ` Simon Marchi
2018-06-18  9:42           ` Nick Clifton
2018-06-15 17:29 ` Joseph Myers
2018-06-16  3:05   ` Simon Marchi
2018-06-18 15:12     ` Joseph Myers
2018-06-18 15:32       ` Simon Marchi
2018-06-16 22:41 ` Andreas K. Huettel

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=df0ee0e1-8e97-ffb6-edb2-c0aee39b262f@redhat.com \
    --to=nickc@redhat.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