From: Andreas Schwab <schwab@linux-m68k.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Alan Modra <amodra@gmail.com>, 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: Sat, 16 Jun 2018 07:17:00 -0000 [thread overview]
Message-ID: <m2bmcbgpzw.fsf@linux-m68k.org> (raw)
In-Reply-To: <8b17a501-41ca-4a7e-ba4d-bc498eb27d85@polymtl.ca> (Simon Marchi's message of "Fri, 15 Jun 2018 23:55:40 -0400")
On Jun 15 2018, Simon Marchi <simon.marchi@polymtl.ca> wrote:
> 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.
You always need to run automake (and the other autotools) in the
directory containing the configure.ac file (top_srcdir in automake
speak). If you configure with --enable-maintainer-mode the needed rules
are run automatically.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2018-06-16 7:17 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 [this message]
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=m2bmcbgpzw.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.com \
--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