Re: [Mingw-w64-public] Runtime for Cygwin

2013-06-05 Thread Kai Tietz
2013/6/5 dw : > >> When using latest mingw-w64 runtime from trunk for Cygwin I have >> error: http://pastebin.com/9WVgE1Gu > > I would like to experiment with some alternate solutions to what ktietz > proposed, but I need to be sure I understand what is going wrong. > > My attempts to reproduce the

[Mingw-w64-public] pthread_sigmask in winpthreads

2013-06-05 Thread Erik van Pienbroek
Hi, In our quest to enable winpthreads in Fedora we've stumbled across a new issue. Libvirt fails to build with this linker error: CCLD libvirt.la ./.libs/libvirt_driver_remote.a(libvirt_net_rpc_client_la-virnetclient.o): In function `virNetClientIOEventLoop': /builddir/build/BUILD/libvirt-0

[Mingw-w64-public] [PATCH] Add IInspectable and IActivationFactory IDLs

2013-06-05 Thread Rafaël Carré
--- mingw-w64-headers/Makefile.am | 2 + mingw-w64-headers/Makefile.in | 2 + mingw-w64-headers/include/activation.h| 132 ++ mingw-w64-headers/include/activation.idl | 16 +++ mingw-w64-headers/include/inspectable.h | 178 +++

Re: [Mingw-w64-public] Runtime for Cygwin

2013-06-05 Thread dw
Ok, I get it now. As everyone was trying to tell me (including myself), the problem was in SIZE_T/size_t. I just couldn't get my head around the fact that these two lines are different: typedef unsigned long int size_t; typedef unsigned long long SIZE_T; Under CygWin64, they are both

[Mingw-w64-public] Is it the gcc or mingw64 that cause the failure of wx building?

2013-06-05 Thread zhangxinghai
HI,recently I tried several mingw and mingw-w64 version to build wx 2.9.4 http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb /gcc-4.8-release/i686-w64-mingw32-gcc-4.8.0-win32_rubenvb.7z/download ..failed mingw64+gcc4.8 http://www.drang

Re: [Mingw-w64-public] Runtime for Cygwin

2013-06-05 Thread Kai Tietz
No, this patch isn't ok. The type size_t isn't adequate for platform-headers. AFAI researched prototype in platform-header is using SIZE_T. The existing prototypes have to remain in winnt.h header. The prototype of the inline-function has to match the signature of the existing and valid prototyp

Re: [Mingw-w64-public] Is it the gcc or mingw64 that cause the failure of wx building?

2013-06-05 Thread asmwarrior
On 2013-6-6 14:01, zhangxinghai wrote: > HI,recently I tried several mingw and mingw-w64 version to build wx 2.9.4 > http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb > /gcc-4.8-release/i686-w64-mingw32-gcc-4.8.0-win32_rubenvb.7z/download > .

Re: [Mingw-w64-public] Runtime for Cygwin

2013-06-05 Thread dw
> AFAI researched prototype in platform-header is using SIZE_T. The question is, which header do you want to be consistent with? Even files within the PSDK don't agree. From the platform sdk winnt.h we see: VOID __stosb ( __out_ecount_full(Count) PBYTE Destination, __in BYTE Value,

Re: [Mingw-w64-public] Runtime for Cygwin

2013-06-05 Thread Kai Tietz
2013/6/6 dw : > >> AFAI researched prototype in platform-header is using SIZE_T. > The question is, which header do you want to be consistent with? Even > files within the PSDK don't agree. > > From the platform sdk winnt.h we see: > > VOID > __stosb ( > __out_ecount_full(Count) PBYTE Destin