On Thu, June 8, 2006 06:35, Sheets, Jason (Manpower Contract) wrote: > Hi Bart, thanks for the tip, I tried adding wsock32 in every order I > could contemplate and still failed to find select.
The configure script should check for both anyway, so I guess the one bit of good news is that apparently it's not that logic per se that's at fault here. >From what I understand so far, which is very little, building sockets programs on Windows is a complicated matter with multiple libraries to choose from etc. Do you have any idea what library you would normally use to build programs using select() or other standard socket calls in this environment? Once we have a library name, adding it to the configure script should be a piece of cake. Oh, but just in case, it may be worthwhile to have a look at your config.log, just to make sure that there aren't any unrelated errors foiling the select() check. The script relies on compile failures in a little test program to mean that select() is not available--but it can't distinguish between that and other errors. It should be safe to attach it to your message; the list software should filter it out if it's awkwardly big, but I will still get a copy as long as I'm on your Cc: list separately. Jeroen _______________________________________________ Libpqxx-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
