From: Eli Zaretskii <eliz@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: 17258@debbugs.gnu.org
Subject: bug#17258: autogen.sh doesn't update stale autoconf files in build-aux
Date: Sun, 13 Apr 2014 14:39:45 +0300 [thread overview]
Message-ID: <83ppkllapq.fsf@gnu.org> (raw)
In-Reply-To: <8761md1n6k.fsf@Rainer.invalid>
> From: Achim Gratz <Stromeko@nexgo.de>
> Date: Sun, 13 Apr 2014 13:30:43 +0200
>
> [would you please not quote full email addresses?]
[Why? And it's not me, it's Emacs. And the list server mangles them
anyway.]
> Eli Zaretskii writes:
> >> My expectation would be that any call to autogen.sh would re-create
> >> these files.
> >
> > That's not enough (assuming we indeed want these files to be
> > re-created automatically): just running "make" will invoke the
> > autotools as needed. In fact, after the initial invocation of
> > autogen.sh, you should normally never again need to run it by hand.
>
> The Makefile (at least on GNU/Linux) actually calls autotools through
> autogen.sh and not directly.
GNUMakefile does, but not Makefile.in:
$(srcdir)/configure: $(AUTOCONF_INPUTS)
cd ${srcdir} && autoconf
ACLOCAL_INPUTS = $(srcdir)/configure.ac $(srcdir)/m4/gnulib-comp.m4
$(srcdir)/aclocal.m4: $(ACLOCAL_INPUTS)
cd $(srcdir) && aclocal -I m4
AUTOMAKE_INPUTS = $(srcdir)/aclocal.m4 $(srcdir)/lib/Makefile.am \
$(srcdir)/lib/gnulib.mk
$(srcdir)/lib/Makefile.in: $(AUTOMAKE_INPUTS)
cd $(srcdir) && automake --gnu -a -c lib/Makefile
next prev parent reply other threads:[~2014-04-13 11:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 9:17 bug#17258: autogen.sh doesn't update stale autoconf files in build-aux Achim Gratz
2014-04-13 10:19 ` Eli Zaretskii
2014-04-13 10:50 ` Achim Gratz
2014-04-13 11:02 ` Eli Zaretskii
2014-04-13 11:30 ` Achim Gratz
2014-04-13 11:39 ` Eli Zaretskii [this message]
2014-04-14 5:45 ` Paul Eggert
2014-04-14 17:14 ` Achim Gratz
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83ppkllapq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17258@debbugs.gnu.org \
--cc=Stromeko@nexgo.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).