Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Alan Modra <amodra@gmail.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>,
	gdb-patches@sourceware.org,        binutils@sourceware.org
Subject: Re: [PATCH] gdb: Update autotools version used for gnulib import
Date: Mon, 07 May 2018 14:28:00 -0000	[thread overview]
Message-ID: <7bced953b160e7baa38ccbac73824d3f@polymtl.ca> (raw)
In-Reply-To: <20180507061528.GR28782@bubble.grove.modra.org>

On 2018-05-07 02:15, Alan Modra wrote:
> On Fri, May 04, 2018 at 02:42:17PM -0400, Simon Marchi wrote:
>> ChangeLog:
>> 
>> 	* ar-lib: New file.
>> 
>> gdb/ChangeLog:
>> 
>> 	* update-gnulib.sh (AUTOCONF_VERSION): Bump to 2.69.
>> 	(AUTOMAKE_VERSION): Bump to 1.16.1.
>> 	* configure.ac: Modernize usage of AM_INIT_AUTOMAKE.
>> 	(AC_PREREQ): Bump to 2.69.
>> 	* import/Makefile.in: Re-generate.
>> 	* aclocal.m4: Re-generate.
>> 	* config.in: Re-generate.
>> 	* configure: Re-generate.
> 
> If this goes in you'll need two versions of autotools for gdb, the new
> one for gdb and the old one for bfd, opcodes, and other dirs.  I'm not
> against the patch BTW, just that it would make sense to update all of
> binutils-gdb.

Ah, I thought that we already needed two different versions for GDB, 
because of this line in gdb/configure.ac:

   AC_PREREQ(2.59)

But the real requirement is 2.64, and seems to come from 
config/override.m4 (not sure how it's invoked though).  This applies to 
all projects under binutils-gdb, but also in the gcc source repository, 
doesn't it?  So we would need to change all of binutils-gdb and gcc at 
the same time, in sync?

Simon


  reply	other threads:[~2018-05-07 14:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-04 18:44 Simon Marchi
2018-05-04 19:34 ` Simon Marchi
2018-05-07  6:15 ` Alan Modra
2018-05-07 14:28   ` Simon Marchi [this message]
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
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=7bced953b160e7baa38ccbac73824d3f@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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