On Thu, Dec 30, 2010 at 10:52, Rich Shepard <[email protected]> wrote:
> On Thu, 30 Dec 2010, chris (fool) mccraw wrote:
>
>> so what does config.log say?
>
> Chris,
>
>   I never noticed this before. That's valuable to know. Thanks.

yup.  it revolutionized my world.  but then i came from a history of
working with substandard unices (aix version 3, early post-sunos
solaris, irix, and some other really weird crusty one-offs back in the
90's), where configure is almost guaranteed to fail.  or anyway, was
back in the 90's.  most open source software has typically built
better on linux than commercial unices in my experience.


>> 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:

there will be a lot of "failures" as it checks for things that aren't
on your system.  but the ones we care about are the ones that prevent
the script from continuing.

> 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'

and there's the only important problem.  looks like another library
might be needed for libsqlite3 to be used successfully.  dunno what
library has those symbols in--whatever it is isn't on my system.  but
you can check yours with the following bash snippit:

for i in /usr/lib/*so ; do nm $i | grep lsym | grep T && echo $i ; done

if you get some output like this:

00000000 T lsym
/usr/lib/libdl.so

(i fabricated that example output.  but it's what you're looking for,
with probably a different library name after)

then you've probably found a library you need to add to $LDFLAGS (in
linker syntax--something like "-ldl") before running ./configure again
(remove config.cache first!)

from the missing function names i'd guess something like libdl, but
mine only has dlsym dlopen, etc, so i don't know.  presumably your
system has the right library on if other sqlite programs that are
dynamically linked work fine, configure just isn't including it
automatically.

luck++;
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to