[LLVMbugs] [Bug 18569] New: Clang bootstrap should work with LLVM_ENABLE_LIBCXX

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=18569

            Bug ID: 18569
           Summary: Clang bootstrap should work with LLVM_ENABLE_LIBCXX
           Product: clang
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: samsonov at google.com
                CC: chandlerc at gmail.com, eugeni.stepanov at gmail.com,
                    hhinnant at apple.com, kcc at google.com,
                    llvmbugs at cs.uiuc.edu, mclow.lists at gmail.com
    Classification: Unclassified

Currently, the following process doesn't work:
(1) Build LLVM/Clang/libc++ using a host compiler (e.g. some version of gcc).
(2) Build Clang again with just-built Clang and -DLLVM_ENABLE_LIBCXX=ON.

I see a number of problems:
(1) Clang doesn't find libc++ if it's not installed in the system, but is
instead located in Clang build directory (or is a part of Clang installation).
See Chandler's comments in r199632 thread. tl;dr libc++ was always thought to
be a part of OS or system root, but not a part of compiler distribution. But we
still want to locate it somehow if it's built together with the compiler.

(2) Configuration problem.
$ cat cxxabi_test.cc 
#include <cxxabi.h>
$ clang++ cxxabi_test.cc -c -o a.o
$ clang++ cxxabi_test.cc -c -o a.o -stdlib=libc++
cxxabi_test.cc:1:10: fatal error: 'cxxabi.h' file not found

As a result at configuration time we find cxxabi.h header, but we can't locate
it when we actually compile the project sources with -stdlib=libc++

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20140121/8ee8bda1/attachment.html>