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

Re: RedHat 5.4 / CentOS 5.4 upgrade to Subversion 1.6.9 - SQLite compiled for 3.6.13, but running with 3.3.6

From: Campbell Allan <campbell.allan_at_sword-ciboodle.com>
Date: Fri, 12 Mar 2010 11:36:15 +0000

On Friday 12 Mar 2010, Marcus Schultheiss wrote:
> Hello,
>
> does anybody do have any hints on this issue regarding CentOS 5.4.
> How to upgrade to 1.6.9 but not break Distribution - SQLite 3.3.6 =>
> 3.6.13.
>
> A work-a-round (e.g. get LD_LIBRARY_PATH to work would help too)
>
> any help is appreciated!
>
> - Marcus
>

Have you tried compiling with static libraries or at least partially static?
I've been building trunk using --disabled-shared on the configure line so
that it doesn't get confused with my existing 1.5 install (I need this for
product compatibility). ldd on the new binary only shows dynamic linker
dependencies on base system libraries (libc, libz etc). nm -a svn | grep -i
sql shows a lot of sqlite entries so that might work for you.

I also just tried a fully static binary by adding --enable-all-static to the
configure line. The line needed a little bit of tweaking (I built zlib from
the bundled subversion-deps tarball). The full command after that was

LDFLAGS=-L`pwd`/zlib ./configure --prefix=/usr/local/subversion-7 --with-neon --with-ssl --disable-shared --enable-all-static --with-zlib=`pwd`/zlib

I don't know if the --with-zlib is still necessary but it does generate a
fully static binary :)

Campbell

> On Fri, Mar 5, 2010 at 11:12 AM, Marcus Schultheiss
>
> <marcus.dev2010_at_googlemail.com> wrote:
> > Hello,
> >
> > having problems to upgrade to Subversion 1.6.9 on CentOS 5.4 (x86_64)
> > system.
> > I am able to compile subversion (agains sqlite 3.6.13) and install.
> > svn command looks fine but using svnadmin does not work
> > # /usr/local/bin/svnadmin create /tmp/test1
> > svnadmin: SQLite compiled for 3.6.13, but running with 3.3.6
> >
> > # ldd /usr/local/bin/svnadmin| grep sqlite
> >     libsqlite3.so.0 => /usr/lib64/libsqlite3.so.0 (0x0000003f7a400000)
> >
> > trying to fix:
> > # export LD_LIBRARY_PATH=/usr/local/lib64
> > # ls -al /usr/local/lib64/libsqlite3.so.0
> > lrwxrwxrwx 1 root root 19 Mar  4 18:16 /usr/local/lib64/libsqlite3.so.0
> > -> libsqlite3.so.0.8.6
> > # ldd /usr/local/bin/svnadmin| grep sqlite
> >     libsqlite3.so.0 => /usr/lib64/libsqlite3.so.0 (0x0000003f7a400000)
> > # echo $LD_LIBRARY_PATH
> > /usr/local/lib64
> >
> >
> > for some unkown reason LD_LIBRARY_PATH work-a-round is not working
> >
> > I could not remove system provided sqlite 3.3.6 because there are
> > dependencies to RPM and so on.
> > I do not want to break other tools.
> >
> > - Marcus

-- 
__________________________________________________________________________________
Sword Ciboodle is the trading name of ciboodle Limited (a company 
registered in Scotland with registered number SC143434 and whose 
registered office is at India of Inchinnan, Renfrewshire, UK, 
PA4 9LH) which is part of the Sword Group of companies.
This email (and any attachments) is intended for the named
recipient(s) and is private and confidential. If it is not for you, 
please inform us and then delete it. If you are not the intended 
recipient(s), the use, disclosure, copying or distribution of any 
information contained within this email is prohibited. Messages to 
and from us may be monitored. If the content is not about the 
business of the Sword Group then the message is neither from nor 
sanctioned by us.
Internet communications are not secure. You should scan this
message and any attachments for viruses. Under no circumstances
do we accept liability for any loss or damage which may result from
your receipt of this email or any attachment.
__________________________________________________________________________________

Received on 2010-03-12 12:36:54 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.