On Thu, 30 Dec 2010, chris (fool) mccraw wrote:
> so what does config.log say? that's where you'll find the actual
> output from the tests, including stderr that might tell you about
> missing files, compilation troubles, and indeed even show you the code
> that configure is attempting to compile before throwing that error.
> (i make the assumption that this test is a compilation test--most that
> ./configure does are, even just checking for include files is usually
> done not by looking for the file on the filesystem but trying to use
> it in via the compiler in some dummy code)
Chris,
I never noticed this before. That's valuable to know. Thanks.
> if you're going to include config.log here, don't send us the whole
> file, just the part where the last tests fail. you can leave off the
> last many lines too--we don't need to know all the values of the
> variables and all that jazz, just what the script is running right
> before it announces those failures (should include code, a command
> line for compiling, and the output from that attempt).
Interesting. conftest fails because it's not a Windows system and there's
no cygwin or win32, but that's earlier in the file. Here's the tail:
configure:10149: checking for sqlite3_open in -lsqlite3
configure:10166: gcc -o conftest -g -O2 -L/usr/lib/ -Wl,--export-dynamic
conftest.c -lsqlite3 -lm 1>&5
/usr/lib//libsqlite3.so: undefined reference to lsym'
/usr/lib//libsqlite3.so: undefined reference to lerror'
/usr/lib//libsqlite3.so: undefined reference to lopen'
/usr/lib//libsqlite3.so: undefined reference to lclose'
collect2: ld returned 1 exit status
configure: failed program was:
#line 10155 "configure"
#include "confdefs.h"
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char sqlite3_open();
I can run sqlite3 from the command line so I have assumed that
libsqlite3.so is complete.
Thanks,
Rich
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
