Compilation error.

Hello!

I compiled llvm clang according to this guide on Unix with GNU GCC 4.6 (Debian gcc package). And I have this error:

llvm[4]: Compiling CGExprAgg.cpp for Debug+Asserts build
/tmp/ccE1jciA.s: Assembler messages:
/tmp/ccE1jciA.s:88098: Error: unknown pseudo-op: .loog' make[4]: *** [/home/kron/Software/llvm/154138/tools/clang/lib/CodeGen/Debug+Asserts/CGExprAgg.o] Error 1 make[4]: Leaving directory /home/kron/Software/llvm/154138/tools/clang/lib/CodeGen’
make[3]: *** [CodeGen/.makeall] Error 2
make[3]: Leaving directory /home/kron/Software/llvm/154138/tools/clang/lib' make[2]: *** [all] Error 1 make[2]: Leaving directory /home/kron/Software/llvm/154138/tools/clang’
make[1]: *** [clang/.makeall] Error 2
make[1]: Leaving directory `/home/kron/Software/llvm/154138/tools’
make: *** [all] Error 1

Respectfully,
Itun

Hello

I compiled llvm clang according to this guide on Unix with GNU GCC 4.6
(Debian gcc package). And I have this error:

llvm[4]: Compiling CGExprAgg.cpp for Debug+Asserts build
/tmp/ccE1jciA.s: Assembler messages:
/tmp/ccE1jciA.s:88098: Error: unknown pseudo-op: `.loog'

Looks like your gcc / compiler is somehow broken.

Check your installation. Debian has unwisely gone ahead with gcc-4.7 migration in Sid that doesn’t grab the libstdc++6 for 4.7 if you upgrade Sid on any general basis.

They were testing in experimental a new clang-3.1 trunk but mysteriously pulled it.

Unfortunately, Clang isn’t 4.7 clean from what I can tell and Debian has already started moving Sid to build against gcc-4.7 leaving one screwed until Clang handles the following:

mdriftmeyer@horus:~/DeveloperProjects/LLVMProject/cmake-clang-llvm$ /usr/local/bin/clang++ …/Hello.World.cpp
In file included from …/Hello.World.cpp:1:
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.7/…/…/…/…/include/c++/4.7/iostream:39:
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.7/…/…/…/…/include/c++/4.7/ostream:39:
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.7/…/…/…/…/include/c++/4.7/ios:42:
In file included from /usr/lib/gcc/x86_64-linux-gnu/4.7/…/…/…/…/include/c++/4.7/bits/ios_base.h:40:
/usr/lib/gcc/x86_64-linux-gnu/4.7/…/…/…/…/include/c++/4.7/ext/atomicity.h:48:12: error: first argument to
atomic operation must be a pointer to _Atomic type (‘volatile _Atomic_word *’ (aka ‘volatile int *’)
invalid)
{ return __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); }
^ ~~~~~
/usr/lib/gcc/x86_64-linux-gnu/4.7/…/…/…/…/include/c++/4.7/ext/atomicity.h:52:5: error: first argument to
atomic operation must be a pointer to _Atomic type (‘volatile _Atomic_word *’ (aka ‘volatile int *’)
invalid)
{ __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); }
^ ~~~~~
2 errors generated.
mdriftmeyer@horus:~/DeveloperProjects/LLVMProject/cmake-clang-llvm$

Backing out, by hand, down to a strict gcc-4.6 install is a pain in the rear presently with Debian. Personally, I’m punting until stuff gets clean up.

  • Marc