Stefan Sperling wrote:
> On Wed, Mar 11, 2009 at 04:54:12PM -0400, John Peacock wrote:
>> I suspect what is going on is that svnversion is not using the in-tree
>> libraries nor is it using the "installed into a temporary path"
>> libraries, but instead is using the already installed older libraries.
>
> That this is a common problem with libtool.
> If you delete the subversion 1.5 package from your system
> before compiling the 1.6 package, things will probably work
> just fine.
Yeah, not an option; we're building RPM's to install our toolchain in
custom locations for a reason. We have other packages that depend on
Subversion and I don't intend to nuke my machine (and the other 10
platform/architectures) every time we need to build a new package.
I wonder if it would be possible to move the generation of this file to
an earlier stage (i.e. before libtool has recompiled everything for the
installed location). Note also that this code is marked:
> ### HACK!! Find a better way to do this
> revision-install:
> subversion/svnversion/svnversion $(top_srcdir) /repos/svn/trunk > $(DESTDIR)$(includedir)/subversion-1/svn-revision.txt
and dates to this commit:
> r4346 | philip | 2003-01-11 11:54:06 -0500 (Sat, 11 Jan 2003) | 18 lines
>
> New program svnversion that generates a compact "current revision" for
> a working copy. Use a quick hack to put the revision in a file in the
> installed include dir (that's ugly, I'm sure someone will be able to do
> something much neater).
I can't find anything in the source tree that even references this file
(if anything ever did).
John
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1310178
Received on 2009-03-12 01:40:19 CET