[wx-dev] [CVS HEAD] Compile error in include/wx/datetime.h

Wlodek Szafran wlodek.szafran at hwcn.org
Tue Apr 10 11:05:31 PDT 2007


On 04/03/2007 4:18 AM, Wlodek Szafran wrote:
> On 04/02/2007 6:20 PM, Vaclav Slavik wrote:
>> Because I removed MinGW and reinstalled it from scratch just to be 
>> sure, and I still don't get this error with the latest MinGW release:
>>     binutils-2.17.50-20060824-1.tar.tar
>>     gcc-core-3.4.5-20060117-1.tar.gz
>>     gcc-g++-3.4.5-20060117-1.tar.tar
>>     mingw-runtime-3.12.tar.gz
>>     w32api-3.9.tar.gz
>> I don't see how could this happen when MinGW doesn't have external 
>> dependencies that could be different in our cases.
> 
> The only differences I can think of now are that I'm using newer 
> binutils, but that shouldn't matter at all and that mine is actually a 
> cross-toolchain hosted on Cygwin, which again shouldn't matter as the 
> type definitions used are those of the target system.

One step further.

There is one other difference which I dismissed before, as after I 
quoted verbatim the command-line I used, I assumed that you used the 
same flags as I did.  Now I see that that wasn't the case.

With the pre-compiled native MinGW GCC 3.4.5, as well as with the 
self-built cross-compiled 3.4.5 hosted on Cygwin, the error only occurs 
when the -pedantic flag is used.  You must've compiled the code without 
that flag, I've compiled with it, that's why we had different results. 
For the record, when I remove that flag from the command-line, the 
compiler doesn't complain.

The newer versions (4.x series) of GCC though, getting less permissive 
and more aggressive about strictly implementing the requirements of the 
language standard, issue the error even without the -pedantic flag.

I'll be (time permitting) looking into this further.

Best regards.

-- 
Wlodek Szafran




More information about the wx-dev mailing list