autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Remove the autoreconf-provided INSTALL, so that we regenerate it.


From: Ralf Wildenhues
Subject: Re: Remove the autoreconf-provided INSTALL, so that we regenerate it.
Date: Sun, 11 Nov 2007 21:39:23 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

* Jim Meyering wrote on Sun, Nov 11, 2007 at 09:16:46PM CET:
> 
>       Remove the autoreconf-provided INSTALL, so that we regenerate it.
>       * GNUmakefile (dummy): Remove INSTALL.

Thanks.

> --- a/GNUmakefile
> +++ b/GNUmakefile
> @@ -47,13 +47,14 @@ include Makefile
>  # for others: rerunning autoconf and recompiling everything isn't cheap.
>  # The $(MAKE) clean is required, to remove all traces of the previous
>  # version string, which would otherwise cause a few test failures.
> +# Remove the autoreconf-provided INSTALL, so that we regenerate it.
>  ifeq (0,$(MAKELEVEL))
>    _is-dist-target = $(filter dist% alpha beta major,$(MAKECMDGOALS))
>    ifneq (,$(_is-dist-target))
>      _curr-ver := $(shell build-aux/git-version-gen $(srcdir) .version)
>      ifneq ($(_curr-ver),$(VERSION))
>        $(info INFO: running autoreconf for new version string: $(_curr-ver))
> -      dummy := $(shell rm -rf autom4te.cache; autoreconf -i && $(MAKE) clean)
> +      dummy := $(shell rm -rf autom4te.cache; autoreconf -i && $(MAKE) clean 
> && rm -f INSTALL)

I have a question or two for this line: First, can we do `autoreconf -v
-i', so autotools rerun triggers are visible?  I ask because I sometimes
bootstrap with an automake that is not the first in $PATH (released
Automake vs. development version), so it helps seeing when I forgot to
adjust $PATH at time.

Second, is the `rm -rf autom4te.cache;' needed?

Third, isn't there an `cd $(srcdir)' or two missing?

>      endif
>    endif
>  endif

Cheers,
Ralf




reply via email to

[Prev in Thread] Current Thread [Next in Thread]