Re: GCC 5.1.0 in mxe-octave

[Tatsuro MATSUOKA]

----- Original Message -----

> From: Tatsuro MATSUOKA 
> To: tmacchant; John W. Eaton ; Octave Maintainers List <address@hidden>
> Cc: 
> Date: 2015/5/8, Fri 16:35
> Subject: Re: GCC 5.1.0 in mxe-octave
> 
> ----- Original Message -----
> 
>>  From: Tatsuro MATSUOKA 
>>  To: John W. Eaton ; Octave Maintainers List
>>  Cc: 
>>  Date: 2015/5/7, Thu 17:07
>>  Subject: Re: GCC 5.1.0 in mxe-octave
>> 
>>  ----- Original Message -----
>> 
>>>   From: John W. Eaton 
>>>   To: Octave Maintainers List 
>>>   Cc: address@hidden
>>>   Date: 2015/5/7, Thu 05:05
>>>   Subject: GCC 5.1.0 in mxe-octave
>>> 
>>>   I updated mxe-octave and noticed that GCC has been updated to 5.1.0.  
> Is 
>>  this 
>>>   necessary for some bug fixes?  If not, I'd prefer to stay at the 
>>  previous 
>>>   version for the Octave 4.0.x releases.
>>> 
>>>   More generally, how should we manage Octave releases and mxe-octave 
>>>   development?  I'd guess that whatever Octave 4.0.x releases that 
> we 
>>  make 
>>>   should be done with the same set of tools.  Also possibly with the 
> same set 
>>  of 
>>>   packages, with only bug fixes applied, same as we do for the Octave 
>>  releases 
>>>   themselves.  But I don't know that we have a good way of handling 
> that 
>>  as 
>>>   package development proceeds separately from Octave development.
>>> 
>> 
>> 
>>  I point annoying bugs for windows users for those who use non-ascii 
> characters.
>> 
>>  1. Files and directories with non-ASCII characters not handled correctly on 
> 
>>  Windows
>>  http://savannah.gnu.org/bugs/?42036
>> 
>> 
>>  This might come from bug of MinGW compiler handling unicode.
>> 
>>  2.  command window problem for windows for Japanese
>>  http://savannah.gnu.org/bugs/?44538
>> 
>>  (This bug is not only for Japanese but also for Chinese.)
>> 
>>  This might be a problem of handling windows code page.
>> 
>>  The bug 1 seems to be related the mingw-gcc (4.x.x).
>>  If it is solved in 5.1.0, it is worth to use it, I think.
>>  I cannot test gcc 5.1 of the mingw64 project because the 5.1 directories 
> are 
>>  empty.
>> 
>>  BTW, the cygwin version of octave does naturally not suffer any problems of 
> the 
>>  above on octave-3.8.2.
>> 
> 
> 
> Philip privately provided me mxe-octave built by gcc-5.1.0.
> I appreciate Philip's kindness! 
> 
> I executed the test for the above two bugs.  
> The two above problems are unfortunately not solved by gcc version up to 
> 5.1.0.
> 
> Therefore we have to solve the issues independently with gcc(mingw) version.


Philip kindly provided me updated the mxe-octave (4.0.0-rc4 64bit) with gcc 
5.1.0.
However, unfortunately the two bug are not affected by the change.

Tatsuro