[PATCH 1/1] trace: build with c++17 if building against llvm 16+

[Chris Johns]

On 10/11/2023 7:27 pm, Sebastian Huber wrote:
> On 25.09.23 11:25, Sebastian Huber wrote:
>> On 25.09.23 08:45, Chris Johns wrote:
>>> On 22/9/2023 2:47 pm, Sebastian Huber wrote:
>>>> On 22.09.23 04:36, Joel Sherrill wrote:
>>>>> Are we doing something that particularly requires C++17? AFAIK we haven't
>>>>> needed it yet and why wouldn't it also be needed with gcc? If the default on
>>>>> recent gcc versions is that, ok but we should be precise in case an older gcc
>>>>> with a different default is used.
>>>> The problem is not that we use features of a particular standard. It is that
>>>> LLVM requires a particular standard for the header files it ships and that
>>>> we use.
>>>>
>>>> I already fixed this some time ago:
>>>>
>>>> https://lists.rtems.org/pipermail/devel/2023-May/075269.html
>>>>
>>>> However, Chris didn't like the change.
>>> The issue was not specially about that change but the tested hosts. I am fine if
>>> the referenced change builds on a recent MacOS and FreeBSD 13. I am still none
>>> the wiser?
>>
>> Ok, lets wait until the RTEMS Project has the appropriate CI runners to do this.
> 
> The next RTEMS user hit this problem which I fixed May this year:
> 
> http://devel.rtems.org/ticket/4965
> 

Any test results? I am sorry but I have not had time to check.

Chris