checking for sqlite3_open in -lsqlite3... no
checking for sqlite3_open in -lsqlite3... no
configure: error: Could not find libsqlite3
/tmp/minidlna-1.1.2# locate libsqlite3
/usr/lib/libsqlite3.so.0.8.6
/usr/lib/libsqlite3.so.0
/usr/lib/libsqlite3.la
/usr/lib/libsqlite3.so
same place as its always been Justin, but doesn't like this new release...
configure:9143: checking for sqlite3_open in -lsqlite3
configure:9168: gcc -o conftest -g -O2 conftest.c -lsqlite3 >&5
/usr/lib/gcc/i486-slackware-linux/4.4.4/../../../libsqlite3.so: undefined reference to dlsym'
/usr/lib/gcc/i486-slackware-linux/4.4.4/../../../libsqlite3.so: undefined reference todlerror'
/usr/lib/gcc/i486-slackware-linux/4.4.4/../../../libsqlite3.so: undefined reference to dlopen'
/usr/lib/gcc/i486-slackware-linux/4.4.4/../../../libsqlite3.so: undefined reference todlclose'
collect2: ld returned 1 exit status
Hmm, looks like a toolchain issue to me. That should really be handled automatically by your linker. What does
ldd /usr/lib/libsqlite3.solook like?For a quick fix, just adding "LIBS=-ldl" to your configure command line might make it work.
This appears to be a duplicate of bug #207 ("MiniDLNA v1.1.0 configure fails to properly detect libsqlite3"), opened 2013-08-17 and still awaiting resolution.
This appears to be a sqlite3 bug that was fixed over 3 years ago.
http://www3.sqlite.org/cgi/src/info/f69ed286ffb3f62f5cb5c1f7df55fa4d2468b472