Re: [Qemu-devel] [PATCH RFC] configure: fix clang failure for libatomic

On 04/25/2017 10:35 AM, Nikunj A Dadhania wrote: if compile_prog "" "" ; then atomic128=yes + elif compile_prog "" "-latomic" ; then + atomic128=yes + lib_atomic="-latomic" fi This is a problem, because I think you'll find that gcc now advertises CONFIG_ATOMIC128 for

Re: [Qemu-devel] [PATCH RFC] configure: fix clang failure for libatomic

On 25 April 2017 at 10:16, Nikunj A Dadhania wrote: > Peter Maydell writes: > >> On 25 April 2017 at 09:58, Nikunj A Dadhania >> wrote: >>> /tmp/atomic-1660e0.o: In function `main': >>>

Re: [Qemu-devel] [PATCH RFC] configure: fix clang failure for libatomic

Peter Maydell writes: > On 25 April 2017 at 09:58, Nikunj A Dadhania > wrote: >> I was trying out the program in the configure script with clang and I do >> get errors without libatomic: >> >> $ clang /tmp/atomic.c >>

Re: [Qemu-devel] [PATCH RFC] configure: fix clang failure for libatomic

On 25 April 2017 at 09:58, Nikunj A Dadhania wrote: > I was trying out the program in the configure script with clang and I do > get errors without libatomic: > > $ clang /tmp/atomic.c > /tmp/atomic.c:6:7: warning: implicit declaration of function >

Re: [Qemu-devel] [PATCH RFC] configure: fix clang failure for libatomic

Peter Maydell writes: > On 25 April 2017 at 09:35, Nikunj A Dadhania > wrote: >> Travis builds failure was reported for powernv boot-serial test with >> qemu built with clang. >> >> Debugging revealed that CONFIG_ATOMIC64 wasnt getting set

Re: [Qemu-devel] [PATCH RFC] configure: fix clang failure for libatomic

On 25 April 2017 at 09:35, Nikunj A Dadhania wrote: > Travis builds failure was reported for powernv boot-serial test with > qemu built with clang. > > Debugging revealed that CONFIG_ATOMIC64 wasnt getting set for the clang > build because of that atomic operations