sqlite checks and apr

On my Debian/stable system I have apr linked to sqlite 3.3.8 so
configure fails. When it fails I get

  configure: WARNING: no suitable sqlite found

  An appropriate version of sqlite could not be found, so libsvn_ra_local
  will not be built. If you want to build libsvn_ra_local, please either
  install sqlite 3.5.9 on this system

  or

  get sqlite 3.5.9 from:
      http://www.sqlite.org/sqlite-3.5.9.tar.gz
  unpack the archive using tar/gunzip and rename the resulting
  directory from ./sqlite-3.5.9/ to ./sqlite/

  configure: error: Subversion requires SQLite

One problem is that the first part of message seems to indicate that
ra_local is optional. That's not true is it?

Another problem is that the suggestion that I build 3.5.9 in-tree
doesn't seem sensible if I'm using apr linked to sqlite. A build that
links directly to sqlite 3.5.9 while apr links to 3.3.8 is a bit dodgy
isn't it? I think configure should be looking at apr to find out
which, if any, sqlite is already used. That's the way BDB works isn't
it?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-09 01:19:08 CEST