[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn and autoconf

From: Andreas Krey <a.krey_at_gmx.de>
Date: Sat, 19 Nov 2011 17:27:16 +0100

On Sat, 19 Nov 2011 08:32:47 +0000, tsteven4 wrote:
> >configure: configure.in
> > autoconf
> Make has a hard time deciding if it needs to build configure. It ends
> up depending on the order the files were pulled during the "svn co"
> command. My experience on other projects is that you can not count on
> the timestamp order to be consistent. It seems that after a checkout
> make sometimes thinks a target is out of date and other times it doesn't.


> This seems like a general issue with subversion any time a target and a
> dependency of that target are both in the repository.

This is not subversion-specific (except that a similar quirk lurks
in the subversion sources). Putting a target under version control
is the exact opposite of 'source code control'; there will always be
issues with make (or other) dependencies, independent of what time
stamps a checkout produces..

> Does any body know of a good way to resolve this? Clearly I can touch
> configure before I make, but I am looking for a more general and
> automated solution.

Don't put 'configure' under version control. Expect people who use
a checkout to have 'autoconf' installed (yuck).

When producing a release .tar file that shall not use autoconf,
run autoconf, remove the autoconf rule from the makefile, and
tar the result (with or without configure.in).


"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
Received on 2011-11-19 17:27:58 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.