From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Stefano Lattarini <stefano.lattarini@gmail.com>,
Git List <git@vger.kernel.org>,
Martin von Zweigbergk <martinvonz@gmail.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [BUG] Infinite make recursion when configure.ac changes
Date: Wed, 20 Feb 2013 23:59:09 -0800 [thread overview]
Message-ID: <7vbobew10y.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130221062614.GA8827@sigill.intra.peff.net> (Jeff King's message of "Thu, 21 Feb 2013 01:26:14 -0500")
Jeff King <peff@peff.net> writes:
> Anyway, here is the patch to fix the loop.
>
> -- >8 --
> Subject: [PATCH] Makefile: avoid infinite loop on configure.ac change
>
> If you are using autoconf and change the configure.ac, the
> Makefile will notice that config.status is older than
> configure.ac, and will attempt to rebuild and re-run the
> configure script to pick up your changes. The first step in
> doing so is to run "make configure". Unfortunately, this
> tries to include config.mak.autogen, which depends on
> config.status, which depends on configure.ac; so we must
> rebuild config.status. Which leads to us running "make
> configure", and so on.
>
> It's easy to demonstrate with:
>
> make configure
> ./configure
> touch configure.ac
> make
>
> We can break this cycle by not re-invoking make to build
> "configure", and instead just putting its rules inline into
> our config.status rebuild procedure. We can avoid a copy by
> factoring the rules into a make variable.
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
Thanks. This needs to go to both v1.8.1.x and v1.8.2.
Will apply.
> Makefile | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/Makefile b/Makefile
> index 3b2c92c..ee1c0b0 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1871,12 +1871,14 @@ configure: configure.ac GIT-VERSION-FILE
> mv $@+ $@
> endif # NO_PYTHON
>
> +CONFIGURE_RECIPE = $(RM) configure configure.ac+ && \
> + sed -e 's/@@GIT_VERSION@@/$(GIT_VERSION)/g' \
> + configure.ac >configure.ac+ && \
> + autoconf -o configure configure.ac+ && \
> + $(RM) configure.ac+
> +
> configure: configure.ac GIT-VERSION-FILE
> - $(QUIET_GEN)$(RM) $@ $<+ && \
> - sed -e 's/@@GIT_VERSION@@/$(GIT_VERSION)/g' \
> - $< > $<+ && \
> - autoconf -o $@ $<+ && \
> - $(RM) $<+
> + $(QUIET_GEN)$(CONFIGURE_RECIPE)
>
> ifdef AUTOCONFIGURED
> # We avoid depending on 'configure' here, because it gets rebuilt
> @@ -1885,7 +1887,7 @@ config.status: configure.ac
> # do want to recheck when the platform/environment detection logic
> # changes, hence this depends on configure.ac.
> config.status: configure.ac
> - $(QUIET_GEN)$(MAKE) configure && \
> + $(QUIET_GEN)$(CONFIGURE_RECIPE) && \
> if test -f config.status; then \
> ./config.status --recheck; \
> else \
prev parent reply other threads:[~2013-02-21 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 8:44 [BUG] Infinite make recursion when configure.ac changes Stefano Lattarini
2013-02-21 6:04 ` Jeff King
2013-02-21 6:10 ` Junio C Hamano
2013-02-21 6:26 ` Jeff King
2013-02-21 7:59 ` Junio C Hamano [this message]
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=7vbobew10y.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=martinvonz@gmail.com \
--cc=peff@peff.net \
--cc=stefano.lattarini@gmail.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;
as well as URLs for NNTP newsgroup(s).