Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread Martin Storsjö
On Tue, 16 Aug 2016, David Wohlferd wrote: > The next warnings to clean up (unused.patch) are pretty simple. Just a few > unused params. Note that since gs_support.c only leaves the param unused for > ARM, using __UNUSED_PARAM is impractical. This one is fine with me, although I'm not sure if

[Mingw-w64-public] Building mingw-w64 and include paths

2016-08-16 Thread David Wohlferd
One of my upcoming patches is going to be a bit controversial (or maybe I'm just missing something). In either case, I'm going to go ahead and start the discussion early. First a bit of vocabulary. I'm not including this because I think people here don't know these terms. It's because *I* am

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread David Wohlferd
On 8/16/2016 3:34 PM, Jacek Caban wrote: On 8/17/16 12:30 AM, David Wohlferd wrote: Jacek? Ktietz? Where do we stand on my defines3.patch and dxgi2.patch? Approved to push? They are fine with me. Thanks. Pushed. The next warnings to clean up (unused.patch) are pretty simple. Just a few

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread Martin Storsjö
On Tue, 16 Aug 2016, David Wohlferd wrote: On 8/16/2016 7:30 AM, Martin Storsjö wrote: Btw, All of your mails end up sorted in the spam box by gmail (at least for me), citing this reason: "It has a from address in yahoo.com but has failed yahoo.com's required tests for authentication." As lon

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread Jacek Caban
On 8/17/16 12:30 AM, David Wohlferd wrote: > Jacek? Ktietz? Where do we stand on my defines3.patch and > dxgi2.patch? Approved to push? They are fine with me. Thanks, Jacek --

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread David Wohlferd
On 8/16/2016 7:30 AM, Martin Storsjö wrote: > Btw, > > All of your mails end up sorted in the spam box by gmail (at least for > me), citing this reason: "It has a from address in yahoo.com but has > failed yahoo.com's required tests for authentication." > > As long as I remember to check the spam b

Re: [Mingw-w64-public] Autotools & git

2016-08-16 Thread Jim Michaels
a sh.exe would be exceptionally useful since windows does not provide one. - Jim Michaels http://www.JesusnJim.com (computer repair info, programming) *From:* Ruben Van Boxem *To:* Jean-Baptiste Kempf ; "ming

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread The Canadian Bacon
It's because yahoo isn't doing proper dkim signatures, Google up the ante on proper e-mail authentication and security. On Aug 16, 2016 10:32 AM, "Martin Storsjö" wrote: > Btw, > > All of your mails end up sorted in the spam box by gmail (at least for > me), citing this reason: "It has a from ad

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread Martin Storsjö
Btw, All of your mails end up sorted in the spam box by gmail (at least for me), citing this reason: "It has a from address in yahoo.com but has failed yahoo.com's required tests for authentication." As long as I remember to check the spam box, it's fine though :-) // Martin -

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread dw
On 8/16/2016 5:51 AM, Jacek Caban wrote: On 16.08.2016 14:14, dw wrote: cpp_quote("#define MAKE_DXGI_HRESULT(x)MAKE_HRESULT(1, _FACDXGI, x)") +cpp_quote("") +cpp_quote("/* These defines are (incorrectly) duplicated in winerror.h. Avoid the") +cpp_quote(" redefine e

[Mingw-w64-public] [PATCH] winerror.h: Moved WINCODEC_ERR_* defines to winerror.h.

2016-08-16 Thread Jacek Caban
Signed-off-by: Jacek Caban --- mingw-w64-headers/include/wincodec.h | 16 - mingw-w64-headers/include/wincodec.idl | 17 -- mingw-w64-headers/include/winerror.h | 41 ++ 3 files changed, 41 insertions(+), 33 deletions(-) diff --git a/m

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread Jacek Caban
On 16.08.2016 14:14, dw wrote: > cpp_quote("#define MAKE_DXGI_HRESULT(x) > MAKE_HRESULT(1, _FACDXGI, x)") > +cpp_quote("") > +cpp_quote("/* These defines are (incorrectly) duplicated in winerror.h. > Avoid the") > +cpp_quote(" redefine error. */") > +cpp_quote("#ifndef

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread dw
On 8/16/2016 4:34 AM, Martin Storsjö wrote: > On Tue, 16 Aug 2016, dw wrote: > >> Attempting to follow Martin's suggestions, I'm attaching the next three (I >> *think* this is the organization he requested). Ok to push? > uchar.patch and ntsecapi.patch are ok with me. Hearing no objections, I wil

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread Martin Storsjö
On Tue, 16 Aug 2016, dw wrote: > On 8/16/2016 4:16 AM, Jacek Caban wrote: >> On 16.08.2016 12:50, dw wrote: >>> --- a/mingw-w64-headers/include/mfidl.h >>> +++ b/mingw-w64-headers/include/mfidl.h >> This file is auto generated. You should not touch it, please change .idl >> file instead. > > Stric

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread dw
On 8/16/2016 4:16 AM, Jacek Caban wrote: On 16.08.2016 12:50, dw wrote: --- a/mingw-w64-headers/include/mfidl.h +++ b/mingw-w64-headers/include/mfidl.h This file is auto generated. You should not touch it, please change .idl file instead. Strictly speaking, I believe the (duplicate) MF_xx_BYT

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread Martin Storsjö
On Tue, 16 Aug 2016, dw wrote: > Attempting to follow Martin's suggestions, I'm attaching the next three (I > *think* this is the organization he requested). Ok to push? uchar.patch and ntsecapi.patch are ok with me. > = defines.patch > Fix minor variations in definitions

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread Jacek Caban
On 16.08.2016 12:50, dw wrote: > > diff --git a/mingw-w64-headers/include/mfidl.h > b/mingw-w64-headers/include/mfidl.h > index 76e8ae3..1658e58 100644 > --- a/mingw-w64-headers/include/mfidl.h > +++ b/mingw-w64-headers/include/mfidl.h > @@ -3399,12 +3399,12 @@ typedef struct _MFNetCredentialManag

Re: [Mingw-w64-public] mingw64 gcc-6.1.0 hangs when compiling

2016-08-16 Thread Ray Donnelly
Hi Mario, On Mon, Aug 15, 2016 at 11:29 AM, Mario Emmenlauer wrote: > > Dear All, > > I don't know how/where to report this or how to debug the issue, > please let me know what I can do. I tried upgrading protobuf to the > new 3.0.0 release in Alexpux/MINGW-packages. However gcc hangs when > comp

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread dw
On 8/16/2016 12:41 AM, Kai Tietz wrote: From my POV patch is ok. Ok, I pushed that one. Attempting to follow Martin's suggestions, I'm attaching the next three (I *think* this is the organization he requested). Ok to push? BTW, since the list now supports it, I have switched from sending

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread Kai Tietz
Hi, thanks for taking care about those warnings. Interesting that the redefinition is also triggered by whitespace changes, and leading zeros ... but well, I guess it is related to partial parsing, and by comparing for this diagnostic on not unified token stream. From my POV patch is ok. My per

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread Martin Storsjö
On Tue, 16 Aug 2016, dw wrote: On 8/15/2016 11:45 PM, Martin Storsjö wrote: Remove the extra copyright disclaimer headers that you're adding. If you're keen on adding them, send a separate patch for that. I have removed the 'extra' text (attached). Note that I am attaching 2 files, but they

Re: [Mingw-w64-public] Clean build of mingw-w64 (ie no more warning)

2016-08-16 Thread dw
On 8/15/2016 11:45 PM, Martin Storsjö wrote: Remove the extra copyright disclaimer headers that you're adding. If you're keen on adding them, send a separate patch for that. I have removed the 'extra' text (attached). Note that I am attaching 2 files, but they are identical. The goal is to s