Re: [lng-odp] [PATCHv2] configure: libatomic check

2017-02-21 Thread Savolainen, Petri (Nokia - FI/Espoo)
> -Original Message- > From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of > Christophe Milard > Sent: Monday, February 20, 2017 6:10 PM > To: Maxim Uvarov <maxim.uva...@linaro.org> > Cc: LNG ODP Mailman List <lng-odp@lists.linaro.org> >

Re: [lng-odp] [PATCHv2] configure: libatomic check

2017-02-20 Thread Christophe Milard
Hi, If these flags are required for compiling the examples, maybe, they should not be moved to the platform m4. But the problem is maybe more: Why do the examples (which are supposed to be compilable by all) requires this? So maybe this change is good, and will trigger the example question...

Re: [lng-odp] [PATCHv2] configure: libatomic check

2017-02-17 Thread Maxim Uvarov
I need somebody to review this patch. ip frag example required this change to compile in our env. CI things. Looks like ip frag is ready to be merged and this patch is show stopper this that. Thank you, Maxim. On 02/16/17 23:26, Maxim Uvarov wrote: > upcoming patch ip fragmentation example fails

[lng-odp] [PATCHv2] configure: libatomic check

2017-02-16 Thread Maxim Uvarov
upcoming patch ip fragmentation example fails to with gcc 4.8.4 on linking __atomic_compare_exchange_16 functions on x86. For some version of gcc both -latomic and -mcx16 needs to be provided in that case. For clang only -mcx16. That options are set internally for platform but do not set for