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

Re: svnsync_test.py fails: wrong version of SQLite library

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Tue, 23 Nov 2010 20:18:11 -0600

On Tue, Nov 23, 2010 at 6:16 PM, Michael J. Bauer
<mjbauer_at_eecs.tufts.edu> wrote:
> I am attempting to build SVN on a RHEL 5.4 system.  There are two versions
> of SQLite on the system:
>
> * The stock system SQLite, version 3.3.6, with library in /usr/lib
> * A new version of SQLite, version 3.7.3, with library in /usr/sup/lib
>
> I configured SVN with the following options:
>
> ./configure --prefix=/usr/sup/subversion-1.6.13 --with-sqlite=/usr/sup/
>
> (The prefix is because I do not want to clobber the system version of SVN,
> just make a newer one available.)  The build worked without issue; however,
> 'make check' fails.  When I look at the log, I see the following error
> repeatedly:
>
> svnsync: SQLite compiled for 3.7.3, but running with 3.3.6
>
> It looks like svnsync is picking up the wrong version of SQLite, despite
> being compiled with the correct version.  This appears to happen only on
> svnsync synchronize, but I've not exhaustively read through the logs.  I've
> re-run the tests with LD_LIBRARY_PATH, LD_RUN_PATH, and LIBRARY_PATH set
> identically to /usr/sup/lib:/usr/local/lib, to no change in behavior.
>
> To make sure I wasn't missing something, I rebuilt SVN, configuring it with
> explicit environment variables:
>
> ./configure LDFLAGS=-L/usr/sup/lib CPPFLAGS=-I/usr/sup/include
> --prefix=/usr/sup/subversion-1.6.13 --with-sqlite=/usr/sup/
>
> It fails 'make check' in exactly the same way.
>
> When I look at subversion-1.6.13/subversion/svnsync/svnsync, the shell
> script appears to be clobbering the run-time environment variables.  I'm not
> sure this is pertinent, given that it fails with or without the run-time
> variables set, and with or without LDFLAGS and CPPFLAGS set.
>
> How do I get SVN to pick up the correct version of the library on 'make
> check' when --with-sqlite (with or without compile-time and run-time
> environment variables set) doesn't do the right thing?

Have you tried building Subversion with the sqlite amalgamation? You
can point --with-sqlite at an amalgamation file (as downloaded from
sqlite.org), and Subversion will statically include that, removing
library conflicts.

-Hyrum
Received on 2010-11-24 03:18:51 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.