http://llvm.org/bugs/show_bug.cgi?id=16372
Bug ID: 16372
Summary: llvm-config --ldflags does not report -stdlib=libc++
-std=c++11
Product: tools
Version: trunk
Hardware: PC
OS: MacOS X
Status: NEW
Severity: normal
Priority: P
Component: llvm-config
Assignee: unassignedb...@nondot.org
Reporter: jeroen.ket...@yahoo.com
CC: llvmbugs@cs.uiuc.edu
Classification: Unclassified
I'm building libclc [1] against an llvm that was configured and compiled with
the --enable-libcpp and --enable-cxx11 options. As far as I understand this
means that everything I build against this version of llvm needs to be compiled
and linked with -stdlib=libc++ and -std=c++11.
Currently, llvm-config only reports -stdlib=libc++ and -std=c++11 with
--cxxflags, but not with --ldflags. This means that although compilation of
libclc works fine, linking fails with missing symbols, because for linking
libclc only looks at the --ldflags output by llvm-config (which is missing
-stdlib=libc++ and -std=c++11). Standard linkage is against a different (older)
C++ library, as I work on OSX.
My setup is as follows: I'm building llvm with --enable-libcpp and
--enable-cxx11 on OSX using clang as supplied with xcode:
$ clang --version
Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn)
I also compile libclc using the above compiler, whilst pointing to the correct
llvm-config via a command line argument of its configure script.
Note that the libclc developers suggested me to report this problem here
instead fixing this in libclc by passing all cxxflags during the linking stage.
[1] http://libclc.llvm.org/
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
LLVMbugs@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
