emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#17258: closed (autogen.sh doesn't update stale aut


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#17258: closed (autogen.sh doesn't update stale autoconf files in build-aux)
Date: Mon, 14 Apr 2014 05:46:02 +0000

Your message dated Sun, 13 Apr 2014 22:45:15 -0700
with message-id <address@hidden>
and subject line Re: autogen.sh doesn't update stale autoconf files in build-aux
has caused the debbugs.gnu.org bug report #17258,
regarding autogen.sh doesn't update stale autoconf files in build-aux
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
17258: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17258
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: autogen.sh doesn't update stale autoconf files in build-aux Date: Sun, 13 Apr 2014 11:17:16 +0200
While troubleshooting a problem with configure on my system, I found
that autogen.sh never updated these autoconf files in build-aux, so they
were still the same as when they had been generated/copied three years
ago:

build-aux/compile
build-aux/config.guess
build-aux/config.sub
build-aux/install-sh
build-aux/missing
build-aux/depcomp

Apparently these files are just checked for existence unless the
"--force" option is also given (which autogen.sh doesn't do).  I'm
currently using autoconf 2.69 if that matters.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds



--- End Message ---
--- Begin Message --- Subject: Re: autogen.sh doesn't update stale autoconf files in build-aux Date: Sun, 13 Apr 2014 22:45:15 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 In trunk bzr 116975 I changed autogen.sh to use autoreconf's -f option, which should fix the bug. -f won't hurt in the typical case when autogen.sh is being invoked in freshly checked-out sources, and might help in cases where autoreconf itself has been upgraded.

GNU make should do this automatically when things go well, but there are a lot of reasons timestamps can be messed up in a source tree and autogen.sh should try to be helpful when recovering from such problems.


--- End Message ---

reply via email to

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