2013/10/2 Warren Young <war...@etr-usa.com>: > I imagine I could find it with fossil bisect, but I was hoping that just > mentioning the problem here would cause someone close to the > development effort to smack their heads and say "Ah, it must be >sqlite3_foobie_bletch(), which we just added."
Well, I did some digging as well, and it looks like the libtool upgrade is the coolpit: See: <http://www.sourceware.org/autobook/autobook/autobook_88.html> >Historically, the default behaviour of Libtool was as if `-no-undefined' was >always passed on the command line, but it proved to be annoying to >developers who had to constantly turn it off so that their ELF libraries could >be featureful. Now it has to be defined explicitly if you need it. > >There are is a tradeoff: > >If you don't specify `-no-undefined', then Libtool will not build shared >libraries >on platforms which don't allow undefined symbols at link time for such a >library. > >It is only safe to specify this flag when you know for certain that all of the >libraries symbols are defined at link time, otherwise the `-no-undefined' >link will appear to work until it is tried on a platform which requires all >symbols to be defined. Libtool will try to link the shared library in this >case (because you told it that you have not left any undefined symbols), >but the link will fail, because there are undefined symbols in spite of >what you told Libtool. It looks like "-no-undefined" must be added somewhere. Regards, Jan Nijtmans _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
