Re: [Mingw-w64-public] A typo in mingw-w64 headers (winuser.h)

2012-01-05 Thread Ozkan Sezer
On Fri, Jan 6, 2012 at 5:08 AM, Rinrin wrote: > Hi : >  During I'm trying to build QT 4.8 with MinGW-w64, found this issue. > > --- winuser.h.bak       2012-01-06 10:48:26 +0800 > +++ winuser.h   2012-01-06 10:48:45 +0800 > @@ -5309,9 +5309,9 @@ >  #define TOUCHEVENTF_PEN         0x0040 >  #define

[Mingw-w64-public] A typo in mingw-w64 headers (winuser.h)

2012-01-05 Thread Rinrin
Hi : During I'm trying to build QT 4.8 with MinGW-w64, found this issue. --- winuser.h.bak 2012-01-06 10:48:26 +0800 +++ winuser.h 2012-01-06 10:48:45 +0800 @@ -5309,9 +5309,9 @@ #define TOUCHEVENTF_PEN 0x0040 #define TOUCHEVENTF_PALM0x0080 -#define TOUCHEVENTMASKF_TIM

Re: [Mingw-w64-public] Cygwin mingw64-i686-gcc-4.5.3-4: -Wformat warnings broken in C++

2012-01-05 Thread JonY
On 1/6/2012 04:42, Kai Tietz wrote: > 2012/1/5 Christian Franke : >> [Originally sent to Cygwin mailing list] >> >> When printf/scanf functions from MinGW runtime are selected via >> __USE_MINGW_ANSI_STDIO, then format string checking is broken. This only >> affects the C++ compiler: >> >> $ cygche

Re: [Mingw-w64-public] autotools

2012-01-05 Thread JonY
On 1/6/2012 01:29, Alon Bar-Lev wrote: > You should try the mingw package, msys is unmaintained, while the > recent cygwin introduced proper mingw-w64 and recent auto tools which > make it a great alternative. > This really has nothing to do with MSYS, though I do encourage using Cygwin over it o

Re: [Mingw-w64-public] Cygwin mingw64-i686-gcc-4.5.3-4: -Wformat warnings broken in C++

2012-01-05 Thread Kai Tietz
2012/1/5 Christian Franke : > [Originally sent to Cygwin mailing list] > > When printf/scanf functions from MinGW runtime are selected via > __USE_MINGW_ANSI_STDIO, then format string checking is broken. This only > affects the C++ compiler: > > $ cygcheck -f /usr/bin/i686-w64-mingw32-g++ > mingw64

[Mingw-w64-public] Cygwin mingw64-i686-gcc-4.5.3-4: -Wformat warnings broken in C++

2012-01-05 Thread Christian Franke
[Originally sent to Cygwin mailing list] When printf/scanf functions from MinGW runtime are selected via __USE_MINGW_ANSI_STDIO, then format string checking is broken. This only affects the C++ compiler: $ cygcheck -f /usr/bin/i686-w64-mingw32-g++ mingw64-i686-gcc-g++-4.5.3-4 $ cat testfmt.c #

Re: [Mingw-w64-public] autotools

2012-01-05 Thread Alon Bar-Lev
You should try the mingw package, msys is unmaintained, while the recent cygwin introduced proper mingw-w64 and recent auto tools which make it a great alternative. On Thu, Jan 5, 2012 at 7:25 PM, Patrick von Reth wrote: > > Hi the autotools package contains a broken symbolic link, > autotools\s

[Mingw-w64-public] autotools

2012-01-05 Thread Patrick von Reth
Hi the autotools package contains a broken symbolic link, autotools\share\aclocal points to /usr/share/aclocal wont work if extracted with a normal tool. Also if the package gets updated can you please build it with disabled perl threads? The msys-perl doesn't support threads so some autotools oper

Re: [Mingw-w64-public] [Mingw-cross-env-list] difference between your projects

2012-01-05 Thread r . 3
ok thanks! The first link is not working, but the second is verty interesting and seems accurante and maintained. It is too bad it is not indicated in the wiki page of the project about cross compilation! The ultimate thing would be mingw-w64 scripts with mingw-w64 ;-) William - Mail origin

Re: [Mingw-w64-public] [Mingw-cross-env-list] difference between your projects

2012-01-05 Thread Tony Theodore
On 4 January 2012 04:53, wrote: > Dear both lists, > I would like to understand better what is the difference between your two > projects, in term of cross-compilation capabilities (linux -> windows). The main differences are: - mingw-w64 provides headers and runtime that allow you to build bot