- Original Message -
From: "Ozkan Sezer"
>> 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
On Tue, Jul 27, 2010 at 7:37 PM, JonY wrote:
> On 7/27/2010 21:30, Sisyphus wrote:
>> Hi,
>>
>> I have binaries for gcc-4.4.4 20100208 and gcc-4.6.0 20100414
>> (cross-compilers).
>> The former builds libssh2-1.2.6 fine (in msys shell), but the latter
>> doesn't.
>>
>> The errors produced by 4.6.0
On 7/27/2010 21:30, Sisyphus wrote:
> Hi,
>
> I have binaries for gcc-4.4.4 20100208 and gcc-4.6.0 20100414
> (cross-compilers).
> The former builds libssh2-1.2.6 fine (in msys shell), but the latter
> doesn't.
>
> The errors produced by 4.6.0 (during the 'make' stage) are attached in
> m.txt.
>
>
2010/7/27 Sisyphus :
> Hi,
>
> I have binaries for gcc-4.4.4 20100208 and gcc-4.6.0 20100414
> (cross-compilers).
> The former builds libssh2-1.2.6 fine (in msys shell), but the latter
> doesn't.
>
> The errors produced by 4.6.0 (during the 'make' stage) are attached in
> m.txt.
>
> Any ideas on ho
Hi,
I have binaries for gcc-4.4.4 20100208 and gcc-4.6.0 20100414
(cross-compilers).
The former builds libssh2-1.2.6 fine (in msys shell), but the latter
doesn't.
The errors produced by 4.6.0 (during the 'make' stage) are attached in
m.txt.
Any ideas on how this change of behaviour from on
