On Mon, 15 Jan 2018 18:37:47 +0100 Dimitry Andric wrote:
> On 15 Jan 2018, at 11:43, Luca Pizzamiglio wrote:
>> I've already received a couple of messages from pkg-fallout about build
>> failure on head-i386-default [1] [2] both pointing to the same errors,
>> about missing intrinsic symbols rela
On Mon, 15 Jan 2018 17:08:58 + David Chisnall wrote:
> On 15 Jan 2018, at 17:00, Jan Beich wrote:
>> It wouldn't help (see below). Clang 6 accidentally made __atomic* work
>> enough to satisfy configure check but not for the port to build. I guess,
>> it also confuses configure in net/librdka
On 15 Jan 2018, at 11:43, Luca Pizzamiglio wrote:
>
> I've already received a couple of messages from pkg-fallout about build
> failure on head-i386-default [1] [2] both pointing to the same errors,
> about missing intrinsic symbols related to __atomic_*
>
> The clang documentation about C11 ato
Tijl Coosemans writes:
> On Mon, 15 Jan 2018 11:43:44 +0100 Luca Pizzamiglio
> wrote:
>
>> I've already received a couple of messages from pkg-fallout about build
>> failure on head-i386-default [1] [2] both pointing to the same errors,
>> about missing intrinsic symbols related to __atomic_*
>
On Mon, 15 Jan 2018 11:43:44 +0100 Luca Pizzamiglio
wrote:
> I've already received a couple of messages from pkg-fallout about build
> failure on head-i386-default [1] [2] both pointing to the same errors,
> about missing intrinsic symbols related to __atomic_*
>
> The clang documentation about
Hy all,
I've already received a couple of messages from pkg-fallout about build
failure on head-i386-default [1] [2] both pointing to the same errors,
about missing intrinsic symbols related to __atomic_*
The clang documentation about C11 atomic builtins [3] stats that __atomic_*
are GCC extensio
