Re: [dpdk-dev] [PATCH] eal: fix build with conflicting libc variable memory_order

2020-10-15 Thread David Marchand
On Thu, Oct 15, 2020 at 1:16 AM Thomas Monjalon wrote: > > 14/10/2020 08:19, Eli Britstein: > > The cited commit introduced functions with 'int memory_order' argument. > > The C11 standard section 7.17.1.4 defines 'memory_order' as the > > "enumerated type whose enumerators identify memory orderin

Re: [dpdk-dev] [PATCH] eal: fix build with conflicting libc variable memory_order

2020-10-14 Thread Thomas Monjalon
14/10/2020 08:19, Eli Britstein: > The cited commit introduced functions with 'int memory_order' argument. > The C11 standard section 7.17.1.4 defines 'memory_order' as the > "enumerated type whose enumerators identify memory ordering constraints". > Applications that use the standard enum (include

Re: [dpdk-dev] [PATCH] eal: fix build with conflicting libc variable memory_order

2020-10-14 Thread Asaf Penso
>-Original Message- >From: dev On Behalf Of Eli Britstein >Sent: Wednesday, October 14, 2020 9:19 AM >To: dev@dpdk.org >Cc: Eli Britstein >Subject: [dpdk-dev] [PATCH] eal: fix build with conflicting libc variable >memory_order > >The cited commit int

[dpdk-dev] [PATCH] eal: fix build with conflicting libc variable memory_order

2020-10-14 Thread Eli Britstein
The cited commit introduced functions with 'int memory_order' argument. The C11 standard section 7.17.1.4 defines 'memory_order' as the "enumerated type whose enumerators identify memory ordering constraints". Applications that use the standard enum (includes stdatomic.h), will fail compilation wit