From: Ehsan A. <aza...@gm...> - 2010-08-05 15:33:39
|
---------- Forwarded message ---------- From: Ehsan Azarnasab <aza...@gm...> Date: Thu, Aug 5, 2010 at 9:32 AM Subject: Re: [Mingw-w64-public] Change from 4.4.4 to 4.6.0 To: Sisyphus <sis...@op...> On Tue, Jul 27, 2010 at 5:45 PM, Sisyphus <sis...@op...> wrote: > > ----- Original Message ----- > From: "Ozkan Sezer" <se...@gm...> > >>> you're supposed to include winsock2.h before windows.h, as windows.h by >>> default includes the incompatible and older winsock.h. >>> >>> Plenty of software packages make this mistake. You'll need to fix up >>> this assumptions. >> >> Well, I think he is using an old header-set, obviously. > > That's possible, I guess, though the "problem" compiler is a more recent > build than the 4.4.4 that works fine. Is there a simple way of installing a > recent set of headers into this 4.6.0 compiler ? I don't see any current > cross-compiler binaries under automated builds that I can try out - they're > all source distros. > > Making sure that winsock2.h gets included first worked fine, btw. (In > libssh2_priv.h I simply included winsock2.h instead of windows.h.) > > In any case, I can stick with 4.4.4 for the time being. I don't have any > *need* to use 4.6.0, and I can keep this particular glitch in mind if I ever > do switch to that compiler. (Yeah .... right ..... "keep this particular > glitch in mind" .... for about a week ... if that :-) > > Thanks guys. > > Cheers, > Rob > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://ad.doubleclick.net/clk;226879339;13503038;l? > http://clk.atdmt.com/CRS/go/247765532/direct/01/ > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public > Just for future reference; if you have included "windows.h" in so many places or the source control is out of your hand, you can "#define _WINSOCKAPI_" which prevents "windows.h" from using "winsock.h", then you can include "winsock2.h" after "windows.h" |