[rtems-source-builder commit] Fix for GCC 4.9 while building with GCC 6+

[Chris Johns]

On 08/06/2017 15:11, Sebastian Huber wrote:
> On 08/06/17 00:33, Chris Johns wrote:
> 
>> On 07/06/2017 23:23, Sebastian Huber wrote:
>>> +%patch add gcc -p1
>>> https://gcc.gnu.org/git/?p=gcc.git;a=blobdiff_plain;f=gcc/cp/Make-lang.in;h=b09fb02bb4c0d16fc2c842bec4069c033897b5f2;hp=e98beb1e33e4bcc4943361c559ae71b7eb345346;hb=1e5f1089dec3af328fd03125d6778f666d0bd4e4;hpb=88375bb2ba8b9004a9924cdae894d7ff32972652
>>>
>>> +%hash sha512
>>> Make-lang.in-h-b09fb02bb4c0d16fc2c842bec4069c033897b5f2-hp-e98beb1e33e4bcc4943361c559ae71b7eb345346-hb-1e5f1089dec3af328fd03125d6778f666d0bd4e4-hpb-88375bb2ba8b9004a9924cdae894d7ff32972652
>>>
>> This file name is 188 characters in length. While it should not be a problem for
>> other reasons it is starting to reaching the limit of the Windows Win32 API
>> maximum file length. The following ticket comment provides more details:
>>
>> https://devel.rtems.org/ticket/2992#comment:1
>>
>> I think the --rsb-file option and the short hash would work, for example
>> Make-lang.in-h-b09fb02bb4c0 and we can avoid any issues on Windows.
> 
> Something like this
> 
> https://git.rtems.org/rtems-source-builder/commit/?id=2c13f00bf2d26ee50f5b49aa7ee6f05a6cce90c7
> 

Yes and thanks. I think the file names may have worked but it would have
depended on the path were the user starts.

FYI GNU's as fails in a gcc build if the path is exceeded. I am currently
working to remove any issues in the RSB and to get 4.11 stable. I am not sure if
this is worth fixing as a Window 10 build is now available that turns this limit
off.

Chris