Issue 35492 in chromium-os: Compile package dev-libs/glib failure with clang syntax checking

22 views
Skip to first unread message

chrom...@googlecode.com

unread,
Oct 19, 2012, 4:41:43 AM10/19/12
to chromium...@chromium.org
Status: Accepted
Owner: ----

New issue 35492 by car...@google.com: Compile package dev-libs/glib failure
with clang syntax checking
http://code.google.com/p/chromium-os/issues/detail?id=35492

When build package dev-libs/glib with clang syntax checking

USE="chrome_internal" CFLAGS="-clang -print-cmdline" CXXFLAGS="-clang
-print-cmdline" emerge-x86-alex dev-libs/glib

I got a configuration failure or gatomic.c:618:2: error: G_ATOMIC_LOCK_FREE
defined, but incapable of lock-free
atomics.
#error G_ATOMIC_LOCK_FREE defined, but incapable of lock-free atomics.
^

It is because the configuration and gatomic.[hc] depends on gcc specific
__GCC_HAVE_SYNC_COMPARE_AND_SWAP and related implementations.


It can only be fixed with another set of portable lock-free atomic
implementations, or we avoid compiling it with clang.

chrom...@googlecode.com

unread,
Oct 19, 2012, 4:43:24 AM10/19/12
to chromium...@chromium.org
Updates:
Cc: c-compil...@google.com

Comment #1 on issue 35492 by car...@chromium.org: Compile package
dev-libs/glib failure with clang syntax checking
http://code.google.com/p/chromium-os/issues/detail?id=35492

(No comment was entered for this change.)

chrom...@googlecode.com

unread,
Oct 19, 2012, 4:13:34 PM10/19/12
to chromium...@chromium.org

Comment #2 on issue 35492 by asha...@chromium.org: Compile package
dev-libs/glib failure with clang syntax checking
http://code.google.com/p/chromium-os/issues/detail?id=35492

In labels, add area-toolchain.

Also, are you filing a clang bug to get this fixed?

chrom...@googlecode.com

unread,
Jan 9, 2013, 7:11:04 PM1/9/13
to chromium...@chromium.org

Comment #3 on issue 35492 by car...@google.com: Compile package
dev-libs/glib failure with clang syntax checking
http://code.google.com/p/chromium-os/issues/detail?id=35492

The clang upstream bug entry is http://llvm.org/bugs/show_bug.cgi?id=11174.

Reply all
Reply to author
Forward
0 new messages