On Thu, Aug 9, 2012 at 10:15 AM, Tilsley, Jerry M. <jmtils...@st-claire.org> wrote: > All, > > I was able to compile and install the version of SQLite I needed out into the > public area. Then I downloaded the source of an earlier version of > subversion and when I configured, it pulled in the sqlite.h file for the > correct version. Now all is working for ALL my users as expected! > > Thanks, > > Jerry
Unless you installed it as an RPM and block yum from updating subversion, this will break the next time subversion is updated in your basic OS updates or if it is pulled in from dependencies for another component, such as "git2svn". The sqlite.h you are using should not be considered the "correct version", seriously. It is apparently a non-standard, distributed out-of-band version of SQLite and not part of the basic CentOS or RHEL operating system and, in my experienced opinion, should not be used for anything but that propietary software, to avoid precisely such problems. Why is it being found? Is there LD_LIBRARY_PATH being set somewhere with a non-standard path, is /etc/ld.so.conf being set oddly, or does it actually include an out-of-date RPM for SQLite that is triggering these version conflicts?
