Thank you so much for that response Eike, Amazingly my many searches never revealed that web page which would have solved my dramas (in fact doing a quick google now I still can't get it).
By coincidence I solved this myself last night by chance. After further digging around I realised that is was a Winsock linkage problem so related to the Win SDK, and because I had tried everything else I could think of, I decided to uninstall my Win SDK from my custom location (D:\Dev\Win_SDK\) to the standard location (C:\Program Files\Microsoft SDKs\Windows\v6.1). Sure enough it worked fine from there, and now, thanks to your link, I see why. Regards Robert Black 2008/12/27 Eike Rathke <[email protected]> > Hi Robert, > > On Wednesday, 2008-12-24 15:46:34 +1000, Robert Black wrote: > > > All went well for about the first 2 hours. Many modules built and no > > complaints. Then it exits the build with an error in the 'Python' module. > I > > get 3 linker errors: > > > > socketmodule.obj : error LNK2019 unresolved external symbol > > __imp__freeaddri...@4 referenced in function _setipaddr > > socketmodule.obj : error LNK2019 unresolved external symbol > > __imp__getaddri...@16 referenced in function _setipaddr > > socketmodule.obj : error LNK2019 unresolved external symbol > > __imp__getnamei...@28 referenced in function _makeipaddr > > [...] > > > > I am using Visual Studio Express 2008, on Win XP and have tried both > > OOO300_m9 and DEV300_m37 with what appears to be the same result. > > > Seems you're hit by case-significance of MS-SDK's installation directory > within cygwin, see > http://www.openoffice.org/issues/show_bug.cgi?id=88568 and if your > configure call is similar whether lower-casing the version string (e.g. > v6.1 instead of V6.1) helps. > > Eike > > -- > PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. > Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD >
