On Fri, Jun 12, 2009 at 04:34:50PM -0500, Nicolas Williams wrote: > On Fri, Jun 12, 2009 at 10:06:31PM +0100, Dr. David Kirkby wrote: > > [...] > > -lpthread -lc -Wl,-soname -Wl,libsqlite3.so.0 -o .libs/libsqlite3.so.0.8.6 > > > > If the order of libpthread and libc are exchanged, the library can be > > built. In other words, libc needs to be linked before libpthread, not > > the other way around. > > Hmm, that's really odd. On S10 libpthread is an empty filter on libc, > which is a fancy way of saying that all of the code in libpthread moved > to libc and libpthread is just a shell saying as much so that older > programs linked with libpthread can still run. You should not add > -lpthread to the link-edit of any program or shared object in Solaris 10 > or above, but if you did the order in which -lpthread and -lc appear in > the link-edit command-line should make no difference.
I spoke to a Solaris linker engineer, and we both suspect that: a) you're using gld, b) libtool is doing things not apparent from the logs that you've posted, c) gld is choking on Solaris libraries that are filters, of which two that are implicated here are: libpthread (appears explicitly in the output you posted) and libdl (implied by the errors about dlerror and friends). Can you try this with the Solaris ld? Alternatively, you could look into eliminating libtools use of libpthread and libdl, as they are not needed under Solaris 10. Also, you say that GNU binutils are easier to use... we'd love to find out in what specific ways. If there's something about the Solaris ld that you dislike, it might be a bug that we'd gladly fix, but if you don't tell us, we might not learn about it. You should post about such things on tools-link...@opensolaris.org (even if you're working on S10). Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
