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

Re: Problem building with neon 0.11.0

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2001-02-18 02:56:24 CET

On Sat, Feb 17, 2001 at 05:49:19PM -0800, Mo DeJong wrote:
> Cool, it builds now.
> Big thanks to gstein and joe for fixing
> things up, I can now compile subversion
> with neon 0.11.0 when builddir != srcdir.
> This is a minor nit, but did does
> automake need --foreign to avoid this eror?
> Passing --gnu seems to be incorrect since
> there are no ChangeLogs.
> % cd ~/project/build/subversion
> % make clean
> cd /home/mo/project/subversion && aclocal -I ac-helpers
> cd /home/mo/project/subversion && automake --gnu Makefile
> automake: Makefile.am: required file `./ChangeLog' not found
> make: *** [/home/mo/project/subversion/Makefile.in] Error 1

There is a rulr for subversion to make the ChangeLog from cvs log in the
Makefile. The problem is that it doesn't work if you aren't in the CVS
directory. This is something I noticed, but didn't really look into too
deeply when I was previously working on trying to get builddir != srcdir
builds working. The cvs2cl.pl script is what is used. I haven't really
looked at it, but I will take a look now, and see if there is a way to
get it to work. The problem is that the ChangeLog should be created in
the srcdir (since that is where it belongs), but technically, nothing in
the build process should modify anything in srcdir. It should be
possible for srcdir to be on a readonly file system. Maybe we should
skip that technicality for subversion? What do people think?

> Mo DeJong
> Red Hat Inc

Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall

  • application/pgp-signature attachment: stored
Received on Sat Oct 21 14:36:22 2006

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

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