Jeroen T. Vermeulen wrote: > On Fri, January 12, 2007 03:37, Curran Schiefelbein wrote: > >> However, there's an undefined symbol in libpqxx_staticD.lib: >> >> libpqxx_staticD.lib(connection_base.obj) : error LNK2019: unresolved >> external symbol [EMAIL PROTECTED] referenced in function >> [EMAIL PROTECTED]@pqxx@@[EMAIL PROTECTED]@[EMAIL PROTECTED] > >> But config-internal-compiler.h correctly comments out the definition of >> PQXX_HAVE_SYS_SELECT_H. So it should be using the select from winsock2, >> correct? > > Yes, though not for that reason. The PQXX_HAVE_SYS_SELECT_H macro merely > indicates whether you have the <sys/select.h> header file, which isn't > available on some systems. Since you don't seem to have it, the source > file will fall back to (in your case) <winsock2.h>. > > But that's all header files. What you're getting is a link error. > Regardless of what header file promises select(), there should be some > library at link time to provide it. On today's Windows systems that would > be the ws2_32 library. You'll need to link your program to at least > libpqxx, libpq, and libws2_32--in that order. > > If you did link to ws2_32 but in a different order, you may still get > errors like this. Linkers don't remember functions unless somebody's > already asked for them.
AFAIK this is not true for the MSVC++ linker, only for unix-style linkers! Cheers, Bart _______________________________________________ Libpqxx-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
