Re: Debugging gcc 4.9 build failure

----------------------------------------
> Date: Thu, 31 Jul 2014 21:28:57 +0100
> From: [email protected]
> To: [email protected]
> Subject: Re: [MinGW-dvlpr] Debugging gcc 4.9 build failure
>
> On 31/07/14 20:47, John E. / TDM wrote:
>> On 7/31/2014 1:30 PM, David Gressett wrote:
>>> The gcc 4.9.1 build fails in the same place as the 4.9.0
>>> build did; I have abandoned 4.9.0 and will
>>> concentrate on 4.9.1.
>>>
>>> The problem occurs when building the Ada runtime library.
>>> The offender is gcc/ada/adaint.c, which fails to compile because the definitions
>>>
>>> #define UNICODE
>>> #define _UNICODE
>>>
>>> in the dependent include file mingw32.h seem to have no
>>> effect.
>>
>> (A followup to my previous reply to this message)
>>
>> What versions of mingwrt and w32api are you using? I have found all
>> 4.0.x releases up to this point to be problematic, and am still using
>> mingwrt-3.20-2 and w32api-3.17-2.
>
> That's surely prudent advice. 
... snip ...
>
> It is distressing, but I fear that WSL-4 simply is not fit for purpose,
> in its presently released state. For serious development work, I agree
> that mingwrt-3.20-2 and w32api-3.17-2 may be a better choice.

I am using the most recently released, i.e., WSL-4. With what I have seen
while chasing the bug, I agree that it is problematic. I only looked at
the include files that were used by adaint.c, but I found numerous
FIXME notes in the comments and many pieces of 64-bit stuff enclosed in
#ifdef conditions. If some of that got in without the #ifdef, strange
things could certainly happen.

Is reverting to mingwrt-3.20-2 and w32api-3.17-2 as simple as downloading
them and overwriting the problematic files? I suspect that dependencies
would make using the installer a difficult business.
 		 	   		  
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk