On 20/07/23 2:56 pm, Florian Weimer via Libc-alpha wrote:
> * Florian Weimer:
>
>> The test suite currently runs header checks with -D_FORTIFY_SOURCE=3
>> even if the compiler does not support it (such as GCC 11), leading to
>> failures.
>>
>> Has this already been discussed?  Should be resolved before the release


We too noticed the test failures for PowerPC.

*error: #warning _FORTIFY_SOURCE > 2 is treated like 2 on this platform 
[-Werror=cpp]*


> It's a regression introduced yesterday:
>
> commit 30379efad117b85cc56a255cac628d0ad745bfe3
> Author: Adhemerval Zanella<adhemerval.zanella@linaro.org>
> Date:   Wed Jul 19 11:37:01 2023 -0300
>
>      scripts: Add fortify checks on installed headers
>      
>      The _FORTIFY_SOURCE is used as default by some system compilers,
>      and there is no way to check if some fortify extension does not
>      trigger any conformance issue.
>      
>      Checked on x86_64-linux-gnu.
>      
>      Reviewed-by: Carlos O'Donell<carlos@redhat.com>
>
> Thanks,
> Florian
>