On 04/25/12 23:34, Philip Martin wrote: > Alan <al...@fairlite.co.uk> writes: > >> It seems that subversion just tries linking explicitly with -lsqlite3 >> during configure, yet sqlite3 itself may be linked against other >> libraries which need to be pulled in. And this can fail on some systems. >> >> The configure script should use "pkg-config --libs sqlite3" to obtain a >> list of libraries. > Subversion does use pkg-config after first trying /usr. Are you saying > this does not work? If I temporarily remove the library from /usr I see > > configure: checking sqlite library > checking sqlite amalgamation... no > checking sqlite3.h usability... yes > checking sqlite3.h presence... yes > checking for sqlite3.h... yes > checking sqlite library version (via header)... okay > checking for sqlite3_close in -lsqlite3... no > checking sqlite library version (via pkg-config)... 3.7.10 > >
Yes, it doesn't work as you are checking /usr first, yet it should be pkg-config first (or only).... This is what I get.... configure: checking sqlite library checking sqlite3.h usability... yes checking sqlite3.h presence... yes checking for sqlite3.h... yes checking sqlite library version (via header)... okay checking for sqlite3_close in -lsqlite3... no configure: WARNING: no suitable sqlite found in /usr Because the check for sqlite3_close in -lsqlite3 fails as it doesn't have the extra libraries available to link the test case. Alan.
