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>, Nick Clifton <nickc@redhat.com>
Cc: 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: Sat, 16 Jun 2018 03:56:00 -0000	[thread overview]
Message-ID: <8b17a501-41ca-4a7e-ba4d-bc498eb27d85@polymtl.ca> (raw)
In-Reply-To: <20180616013916.GW7660@bubble.grove.modra.org>

On 2018-06-15 09:39 PM, Alan Modra wrote:
> On Fri, Jun 15, 2018 at 03:22:10PM +0100, Nick Clifton wrote:
>> Otherwise so far, my testing has been showing no signs of any real problems.
> 
> The patch looks good to me too.  I did see some generated file
> differences, most of which disappeared when I compiled my own
> autoconf-2.69 rather than using the Ubuntu 18.04 version (which
> apparently has some patches from autoconf-2.70 applied).
> 
> I applied both of your posted patches, ran autoconf in zlib since
> you'd said the posted patch was broken, touched all the files in the
> first patch, then built binutils-gdb with --enable-maintainer-mode.
> Apart from .pot files, these were the files that differed:
> 
> bfd/doc/Makefile.in
> binutils/doc/Makefile.in
> gas/doc/Makefile.in
> gdb/aclocal.m4
> gdb/config.in
> gdb/configure
> gdb/gnulib/aclocal.m4
> gdb/gnulib/configure
> libdecnumber/aclocal.m4
> zlib/configure


1. About aclocal.m4's, there are a bunch more generated from other versions of
automake than 1.15.1:

$ grep -rn "generated automatically by aclocal" | grep -v 1.15.1
gdb/aclocal.m4:1:# generated automatically by aclocal 1.11.6 -*- Autoconf -*-
gdb/gdbserver/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
intl/aclocal.m4:1:# generated automatically by aclocal 1.11.6 -*- Autoconf -*-
sim/arm/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/common/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/d10v/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/erc32/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/h8300/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/m32r/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/mcore/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/mips/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/mn10300/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/sh/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/v850/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/cr16/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/cris/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/frv/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/iq2000/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/m32c/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/m68hc11/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/sh64/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/aarch64/aclocal.m4:1:# generated automatically by aclocal 1.11.6 -*- Autoconf -*-
sim/avr/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/bfin/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/ft32/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/lm32/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/microblaze/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/moxie/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/msp430/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/rl78/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/rx/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-
sim/or1k/aclocal.m4:1:# generated automatically by aclocal 1.15 -*- Autoconf -*-
libdecnumber/aclocal.m4:1:# generated automatically by aclocal 1.11.1 -*- Autoconf -*-

Should I make sure to re-generate all of them?  I was running "autoconf" only, but
it seems like running "autoreconf" will also update aclocal.m4 and config.in if needed.


2. How do I update those */doc/Makefile.in?  When I try to run automake in these
directories, I get:

  automake: error: 'configure.ac' is required

and indeed, there is no configure.ac in the doc directories.

Simon


  reply	other threads:[~2018-06-16  3:56 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 [this message]
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=8b17a501-41ca-4a7e-ba4d-bc498eb27d85@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