Re: [Mingw-w64-public] Making config.guess detect mingw64 platform?

2010-07-27 Thread JonY
On 7/28/2010 07:13, Luis Lavena wrote: > Hello, > > At this time I'm using TDM64 provided 4.5.0 binaries, but before > (using the 32-to-64 compiler) found the same issue. > > Using the standard config.guess (and sub) both 32bits and 64bits are > identified as "i686-pc-mingw32" > > I heard that befo

Re: [Mingw-w64-public] Change from 4.4.4 to 4.6.0

2010-07-27 Thread Sisyphus
- 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

[Mingw-w64-public] Making config.guess detect mingw64 platform?

2010-07-27 Thread Luis Lavena
Hello, At this time I'm using TDM64 provided 4.5.0 binaries, but before (using the 32-to-64 compiler) found the same issue. Using the standard config.guess (and sub) both 32bits and 64bits are identified as "i686-pc-mingw32" I heard that before mingw64 gained it's own identification, but using t

Re: [Mingw-w64-public] Change from 4.4.4 to 4.6.0

2010-07-27 Thread Ozkan Sezer
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

Re: [Mingw-w64-public] Change from 4.4.4 to 4.6.0

2010-07-27 Thread JonY
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. > >

Re: [Mingw-w64-public] Change from 4.4.4 to 4.6.0

2010-07-27 Thread Kai Tietz
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

[Mingw-w64-public] Change from 4.4.4 to 4.6.0

2010-07-27 Thread 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 how this change of behaviour from on

Re: [Mingw-w64-public] Jonathan break build on r2963 due to typo in Makefile.am

2010-07-27 Thread JonY
On 7/27/2010 15:20, Dongsheng Song wrote: > Hi Jonathan, > > Here is the patch: > > Index: Makefile.in > === > --- Makefile.in(revision 2968) > +++ Makefile.in(working copy) > @@ -3697,7 +3697,7 @@ > @LIB64_TRUE@ lib64/libks

[Mingw-w64-public] Jonathan break build on r2963 due to typo in Makefile.am

2010-07-27 Thread Dongsheng Song
Hi Jonathan, Here is the patch: Index: Makefile.in === --- Makefile.in(revision 2968) +++ Makefile.in(working copy) @@ -3697,7 +3697,7 @@ @LIB64_TRUE@ lib64/libks.a lib64/librpcdiag.a lib64/librpchttp.a lib64/li