build failure on Windows

2013-10-03 Thread Peter Bortas @ Pike developers forum
I don't think there is anything in between. 0x502 would probably be a more proper value. It's the last one before 0x600 = Longhorn.

build failure on Windows

2013-10-03 Thread Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum
Server 2256?

build failure on Windows

2013-10-03 Thread Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum
0x501 = XP, 0x502 = Server 2003, 0x5ff = ?

build failure on Windows

2013-10-03 Thread Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
>So I took a look at the code now. Moveing from 2K (0x501) to XP >(0x501) APIs fixed the IPv6 problems. Ok, I've bumped the value to 0x5ff in Pike 7.9.

build failure on Windows

2013-10-02 Thread Peter Bortas @ Pike developers forum
So I took a look at the code now. Moveing from 2K (0x501) to XP (0x501) APIs fixed the IPv6 problems. The next problem is that ssize_t is not in the standard and is apparently not a thing in the MS SDK. Hacked around that by defining it as an int just to get past it. The problem after that is tha

build failure on Windows

2013-10-02 Thread Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
>>Hmm, as a side note, I just noticed that at least the WinSDK 6.0 >> (or rather (of 2007-09-27) has replaced >>the #define of IPPROTO_IPV6 with a corresponding enum. The file also >>requires the #define _WIN32_WINNT to be >= 0x0501 to add the symbol >>to the enum. This means that the (quite a few

build failure on Windows

2013-10-02 Thread Peter Bortas @ Pike developers forum
>Hmm, as a side note, I just noticed that at least the WinSDK 6.0 > (or rather (of 2007-09-27) has replaced >the #define of IPPROTO_IPV6 with a corresponding enum. The file also >requires the #define _WIN32_WINNT to be >= 0x0501 to add the symbol >to the enum. This means that the (quite a few) pla

build failure on Windows

2013-10-02 Thread Peter Bortas @ Pike developers forum
The build image is Windows XP and VC9 (2008), so things are expected to be a bit out of date.

build failure on Windows

2013-10-02 Thread Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
> I'm trying to boot up my old Windows build environment, and I'm getting a > new and exiting build error from master. Haven't looked at the code, but > will do that tomorrow night if no one has done it before then: > > Making static: modules/_Stdio > Compiling modules/_Stdio/udp.c > B:\dists

build failure on Windows

2013-10-02 Thread Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum
Perhaps you don't have IPv6 support? A very brief look into MSDN gives the following, which doens't really answer the question of if it existed before Vista. " On the Microsoft Windows Software Development Kit (SDK) released for Windows Vista and later, the organization of header files has changed

build failure on Windows

2013-10-01 Thread Peter Bortas
I'm trying to boot up my old Windows build environment, and I'm getting a new and exiting build error from master. Haven't looked at the code, but will do that tomorrow night if no one has done it before then: Making static: modules/_Stdio Compiling modules/_Stdio/udp.c B:\dists\Pike-v7.9-sna