On 10/29/2015 05:25 PM, Peter Maydell wrote:
> On 29 October 2015 at 21:20, Laszlo Ersek wrote:
>> On 10/29/15 21:29, John Snow wrote:
>>> Here's a good takeaway quote:
>>>
>>> 'Also, _FORTIFY_SOURCE + glibc + clang is not supported and does not
>>> work (for instance, it relies on __builtin_va_
On 29 October 2015 at 21:20, Laszlo Ersek wrote:
> On 10/29/15 21:29, John Snow wrote:
>> Here's a good takeaway quote:
>>
>> 'Also, _FORTIFY_SOURCE + glibc + clang is not supported and does not
>> work (for instance, it relies on __builtin_va_pack_len and friends,
>> which we have no intention of
Aargh, clicked "Reply" instead of "Reply All". Resending.
On 10/29/15 21:29, John Snow wrote:
>
>
> On 10/29/2015 04:22 PM, John Snow wrote:
>> Clang++ 3.5 on Fedora 22 appears to have difficulty tolerating
>> D_FORTIFY_SOURCE for certain glibc headers, such as stdio.
>>
>> This interferes, curr
On 10/29/2015 04:22 PM, John Snow wrote:
> Clang++ 3.5 on Fedora 22 appears to have difficulty tolerating
> D_FORTIFY_SOURCE for certain glibc headers, such as stdio.
>
> This interferes, currently, with any arm target build.
>
> Work around this by disabling FORTIFY_SOURCE for clang builds
> i
Clang++ 3.5 on Fedora 22 appears to have difficulty tolerating
D_FORTIFY_SOURCE for certain glibc headers, such as stdio.
This interferes, currently, with any arm target build.
Work around this by disabling FORTIFY_SOURCE for clang builds
if a problem is observed.
Newer versions of clang such as
