You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Daniel Richard G." <sk...@iskunk.org> on 2006/02/08 19:28:07 UTC
Problems in Subversion out-of-source-tree build
I am building Subversion 1.3.0 off of a read-only NFS mount. Three problems
arose, all minor:
1. The files in the tarball lack read and/or execute permissions for
"other" users (as if created with umask 027).
2. subversion-1.3.0/ac-helpers/config.{guess,sub} have permissions of 754,
for some odd reason.
3. My build framework specifies a symlinked directory for $(top_srcdir),
which works fine most of the time. Subversion, however, seems a bit
touchy about it when the "revision-install" target is run:
----(begin build log excerpt)----
/mnt/freeport/src/subversion/current/ac-helpers/install-sh -c -d /tmp/freeport30097.tmp/mnt/freeport/arch/linux32/info
subversion/svnversion/svnversion /mnt/freeport/src/subversion/current /repos/svn/trunk > /tmp/freeport30097.tmp/mnt/freeport/arch/linux32/include/subversion-1/svn-revision.txt
'/mnt/freeport/src/subversion/current' not versioned, and not exported
make: *** [revision-install] Error 1
----(end build log excerpt)----
(In this instance, .../current is a symlink to the unpacked Subversion
source tarball.)
This can be fixed in Makefile.in: Rather than passing $(top_srcdir)
directly to svnversion, pass in `cd $(top_srcdir) && /bin/pwd`, which
will report the actual (non-symlink) directory of the source tree. I've
attached a (trivial) patch to this end.
Please Cc: any replies to me, as I am not subscribed to this list.
--Daniel
--
NAME = Daniel Richard G. ## Remember, skunks _\|/_ meef?
EMAIL1 = skunk@iskunk.org ## don't smell bad--- (/o|o\) /
EMAIL2 = skunk@alum.mit.edu ## it's the people who < (^),>
WWW = http://www.******.org/ ## annoy them that do! / \
--
(****** = site not yet online)