On Sat, Nov 19, 2011 at 9:32 AM, tsteven4 wrote:
The build fails because autoconf is not installed:
>
[ ... ]
This seems like a general issue with subversion any time a target and a
> dependency of that target are both in the repository.
>
This isn't new to SVN. We had this problem with CVS, t
On Sat, Nov 19, 2011 at 4:32 PM, tsteven4 wrote:
[...]
> Furthermore, this
> is an option set in the svn config file, not on the command line, so it
> isn't convenient to use it for one command and not another.
I think that '--config-option config:miscellany:use-commit-times=yes'
ought to do it
Andreas Krey wrote on Sat, Nov 19, 2011 at 17:27:16 +0100:
> 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).
Example: tools/dist/release.py in Subversion's trunk.
On Sat, 19 Nov 2011 08:32:47 +, 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
In the beta test spirit I tried something I don't usually do, to build
gpsbabel under cygwin.
17 7:50svn co http://gpsbabel.googlecode.com/svn/trunk/gpsbabel
gpsbabel-svn
18 7:52cd gpsbabel-svn/
19 7:52./configure
20 7:54make
The build fails because autoco
