[SOLVED] What's broken with clang++ and string.h?

tavianator · 2014-11-23 00:23:13

Not sure when this started:

$ cat foo.cpp
#include <cstring>
$ clang++ -c foo.cpp     # Works fine
$ clang++ -O2 -c foo.cpp
In file included from foo.cpp:1:
In file included from /usr/bin/../lib64/gcc/x86_64-unknown-linux-gnu/4.9.2/../../../../include/c++/4.9.2/cstring:42:
/usr/include/string.h:82:1: error: unknown type name '__extern_always_inline'
__extern_always_inline void *
^
/usr/include/string.h:82:24: error: expected unqualified-id
__extern_always_inline void *

...

fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.

Last edited by tavianator (2014-11-23 02:17:58)

Allan · 2014-11-23 00:36:04

The upstream glibc-2.20 branch has one out of a pair of patches backported. I will fix it both upstream and here today.

tavianator · 2014-11-23 02:19:05

Thanks!

Arch Linux

#1 2014-11-23 00:23:13

[SOLVED] What's broken with clang++ and string.h?

#2 2014-11-23 00:36:04

Re: [SOLVED] What's broken with clang++ and string.h?

#3 2014-11-23 02:19:05

Re: [SOLVED] What's broken with clang++ and string.h?

Board footer