[Top][All Lists]

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

Re: bug ? ./configure in bash.git.devel ran twice

From: Alex fxmbsw7 Ratchev
Subject: Re: bug ? ./configure in bash.git.devel ran twice
Date: Sun, 10 Oct 2021 02:21:31 +0200

it may be an unfinished merging from git case
i report it cause i never seen it ago and saw it as a bug / error

i did fresh checkout, again, never seen it ago so

On Sun, Oct 10, 2021, 02:19 Dominique Martinet <asmadeus@codewreck.org>

> Alex fxmbsw7 Ratchev wrote on Sun, Oct 10, 2021 at 02:07:34AM +0200:
> > i cloned, modded config top to coprocs 1 and ran ./configure, that
> finished
> > then i ran make -j 8 but it ran configure on cd <something> && autoconf
> > first make output line, then it gcc ed it
> > i dunno i report cause i see unusual behavior of that configure ran
> twiced
> 'make' checks that configure is more recent than the files that generate
> it (configure.ac, aclocal.m4 and config.h.in) and regenerates it if not:
> $(srcdir)/configure:    $(srcdir)/configure.ac $(srcdir)/aclocal.m4
> $(srcdir)/config.h.in
>         cd $(srcdir) && autoconf
> (this is standards autotools stuff)
> When you extract the sources from a tarball, tar will restore the mtimes
> in the archive so configure will be more recent and autoconf will not
> rerun, but git does not care about individual files timestamps so
> autoconf will likely be needed when cloning from git or when updating
> the files.
> --
> Dominique Martinet | Asmadeus

reply via email to

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