RTEMS Tools on 5 release can't be build with modern LLVM

Chris Johns chrisj at rtems.org
Mon Aug 16 22:20:56 UTC 2021


Looks good and thank you for sorting this out.

Chris

On 17/8/21 1:17 am, Christian MAUDERER wrote:
> Am 16.08.21 um 17:12 schrieb Joel Sherrill:
>> On Mon, Aug 16, 2021 at 10:08 AM Christian MAUDERER
>> <christian.mauderer at embedded-brains.de> wrote:
>>>
>>> Hello Joel,
>>>
>>> Am 16.08.21 um 17:03 schrieb Joel Sherrill:
>>>> On Mon, Aug 16, 2021 at 9:49 AM Christian MAUDERER
>>>> <christian.mauderer at embedded-brains.de> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I noted that I can't build the RTEMS 5 toolchain if I have a modern LLVM
>>>>> installed using the RTEMS source builder. Therefore I would like to
>>>>> backport the patch 37ad446d9dce3 ([1]) to the 5 branch. Is that OK? If
>>>>> someone acknowledges it, I would do the following steps without further
>>>>> review (but of course with testing):
>>>>>
>>>>> 1. Create a ticket for the problem.
>>>>> 2. In rtems-tools: Cherry pick the patch 37ad446d9dce3 to the 5 branch.
>>>>> 3. In rtems-source-builder: Backport the patch 91932d0a0 [2] to the 5
>>>>> branch (or rather re-create it because it will be a different commit and
>>>>> a different hash).
>>>>
>>>> I'm ok with this. I remember doing a patch for the opposite direction.
>>>> I couldn't
>>>> build on an older gcc because it assumed a different language version as
>>>> default. gcc 4.8 as on CentOS 7 assumes C++03. Newer versions assume C++11
>>>> as the base. Similarly newer gcc's seem to default to C11.
>>>
>>> Thanks. I'll wait a bit more before adding the patches in case someone
>>> else want's to object.
>>
>>
>> Good plan.
>>
>>>>
>>>> I posted a few weeks ago that users should really be careful to always use
>>>> -std and consciously pick what they want.
>>>
>>> In this case, the version of the standard depends quite a lot on the
>>> LLVM headers. LLVM seems to love using new features.
>>
>> Then this is probably not the first time we will face this.
> 
> Definitively not. It is only a backport of a patch so I had that problem already
> on another system. I only missed to add it to the 5 branch back then.
> 
> Best regards
> 
> Christian
> 
>>
>> --joel
>>
>>> Best regards
>>>
>>> Christian
>>>
>>>>
>>>> --joel
>>>>
>>>>>
>>>>> Best regards
>>>>>
>>>>> Christian
>>>>>
>>>>> [1]
>>>>> https://git.rtems.org/rtems-tools/commit/?id=37ad446d9dce3438d6d32e1caf56d3fdccdd2ad0
>>>>>
>>>>>
>>>>> [2]
>>>>> https://git.rtems.org/rtems-source-builder/commit/?id=91932d0a0c86400366f9c75a62123b6488ff458a
>>>>>
>>>>> -- 
>>>>> --------------------------------------------
>>>>> embedded brains GmbH
>>>>> Herr Christian MAUDERER
>>>>> Dornierstr. 4
>>>>> 82178 Puchheim
>>>>> Germany
>>>>> email: christian.mauderer at embedded-brains.de
>>>>> phone: +49-89-18 94 741 - 18
>>>>> fax:   +49-89-18 94 741 - 08
>>>>>
>>>>> Registergericht: Amtsgericht München
>>>>> Registernummer: HRB 157899
>>>>> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
>>>>> Unsere Datenschutzerklärung finden Sie hier:
>>>>> https://embedded-brains.de/datenschutzerklaerung/
>>>>> _______________________________________________
>>>>> devel mailing list
>>>>> devel at rtems.org
>>>>> http://lists.rtems.org/mailman/listinfo/devel
>>>
>>> -- 
>>> --------------------------------------------
>>> embedded brains GmbH
>>> Herr Christian MAUDERER
>>> Dornierstr. 4
>>> 82178 Puchheim
>>> Germany
>>> email: christian.mauderer at embedded-brains.de
>>> phone: +49-89-18 94 741 - 18
>>> fax:   +49-89-18 94 741 - 08
>>>
>>> Registergericht: Amtsgericht München
>>> Registernummer: HRB 157899
>>> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
>>> Unsere Datenschutzerklärung finden Sie hier:
>>> https://embedded-brains.de/datenschutzerklaerung/
> 


More information about the devel mailing list