GNOME Bugzilla – Bug 610502
[win32] problems on win-2k, missing reference to freeaddrinfo
Last modified: 2010-08-12 19:21:53 UTC
Appears that gnumeric-1.9.16-20091130.exe was built for XP and above only. When I install and try to run it I get told that ws2_32.dll does not have the entry point freeaddrinfo. I use it on NT-2000 (1.9.4 runs fine). Thank you
Since the source code is available you can compile GNumeric yourself. We do not provide binaries for any other operating systems.
gnumeric-1.9.16-20091130.exe W2KSP4 Install path N:\Program Files\Gnumeric Starting Gnumeric returns: gnumeric.exe - Entry point not found The procedure entry point freeaddrinfo could not be located in the dynamic link library WS2_32.DLL. I can confirm this problem under the same circumstances on my PC. Tom is not the only person still running W2K. From what I read in BUG 601840, the solution has been found and would be quite simple [include the Ws2tcpip.h and Wspiapi.h files] for a developer who already has the build setup to compile. Correct me if I'm mistaken.
M. Gueslow has a point, it's really not gnome's problem. The windows binaries are hosted at http://www.gnome.org/~jody/gnumeric/win32/. If one goes up a level or two, one finds a mailto:jody@gnome.com link. Gnome.com is, by the look, not a free software desktop project, and if Jody was ever moonlighting there he's not anymore. However, the thread is assigned to jody@gnome.org, who has not commented. I suspect it was an oversight. If memory serves, previous downloads from ~jody/gnumeric/win32 (not, alas, ~jody/win32/gnumeric as I said above) have worked on nt2k just fine.
The only reference I can see to freeaddrinfo is via gio. Unfortunately I do not see a copy of Wspiapi.h in any of the mingw package on debian. Tom : the gnome.com was a typo and has been fixed. thanks.
Re freeaddrinfo, see bug 603527.
until we can build with the wspiapi.h this problem will persist, and for now the only place to find it is in a fork of ming not packaged by debian..
*** This bug has been marked as a duplicate of bug 626765 ***