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: Nick Clifton <nickc@redhat.com>,
	gdb-patches@sourceware.org,        binutils@sourceware.org,
	Simon Marchi <simon.marchi@ericsson.com>
Subject: Re: [PATCH 1/2] Bump to autoconf 2.69 and automake 1.15.1
Date: Mon, 18 Jun 2018 03:05:00 -0000	[thread overview]
Message-ID: <53f0aeb6-152e-5d42-947b-dce42ad8c1c0@polymtl.ca> (raw)
In-Reply-To: <20180618024632.GZ7660@bubble.grove.modra.org>

On 2018-06-17 10:46 PM, Alan Modra wrote:
>> 1. About aclocal.m4's, there are a bunch more generated from other versions of
>> automake than 1.15.1:
> [snip]
> 
>> Should I make sure to re-generate all of them?
> 
> Yes, I think that should be done whenever updating the version of
> autotools.

Noted.

> I also just noticed these 1.11 version specifiers that probably should
> be updated to 1.15:
> ./bfd/Makefile.am:AUTOMAKE_OPTIONS = 1.11 no-dist foreign
> ./gas/Makefile.am:AUTOMAKE_OPTIONS = 1.11 dejagnu foreign no-dist subdir-objects
> ./gprof/Makefile.am:AUTOMAKE_OPTIONS = 1.11 foreign no-dist no-texinfo.tex info-in-builddir
> ./opcodes/Makefile.am:AUTOMAKE_OPTIONS = 1.11 foreign no-dist

I simply removed them in my latest version of the patch.  I think it is only useful
to put it if you let the user of you Makefile.am use the version of automake they want,
but want to put a lower bound on the version of automake that will work.  In our case we
force people to use a specific version anyway...

>> 2. How do I update those */doc/Makefile.in?
> 
> Andreas has already given the canonical answer, but something like the
> following should work too.
> 
> cd ~/src/binutils-gdb/bfd && automake-1.15 --foreign doc/Makefile
> cd ~/src/binutils-gdb/binutils && automake-1.15 --foreign doc/Makefile
> cd ~/src/binutils-gdb/gas && automake-1.15 --foreign doc/Makefile

Ok, thanks.  Maintainer mode does update them, but I was wondering how to
do it by hand.

I'll post a new version once the sync-with-gcc patches are merged.

Simon


  reply	other threads:[~2018-06-18  3:05 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 ` [PATCH 1/2] Bump to autoconf 2.69 and automake 1.15.1 Nick Clifton
2018-06-15 14:38   ` 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 [this message]
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=53f0aeb6-152e-5d42-947b-dce42ad8c1c0@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=amodra@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.com \
    --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