[llvm-bugs] [Bug 31540] New: libc++ puts libc++abi headers in wrong place in build area

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=31540

            Bug ID: 31540
           Summary: libc++ puts libc++abi headers in wrong place in build
                    area
           Product: libc++
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: richard-llvm at metafoo.co.uk
                CC: llvm-bugs at lists.llvm.org, mclow.lists at gmail.com
    Classification: Unclassified

libc++'s cmake/Modules/HandleLibCXXABI.cmake copies the libc++abi <cxxabi.h>
into the build area. However, instead of copying it to $BUILD/include/c++/v1,
it copies it to $BUILD/include. That seems broken -- a clang binary in
$BUILD/bin doesn't look there, so running the compiler from the build area
results in our being unable to find <cxxabi.h>, which means that header is not
available in stage2 of a simple bootstrap (with no explicit install step).

The cxxabi.h headers should be put next to the libc++ headers in the build
area, just like they are in the install area. However, this appears to cause
the libc++ build itself to fail, because it /does/ have an include path of
$BUILD/include and /does not/ have an include path of $BUILD/include/c++/v1
(which seems reasonable -- we don't want it including headers from some stale
build of the same library). So either we should put these headers in both
places in the build area, or when building libc++ it should pick up cxxabi.h
directly from $SRC/projects/libcxxabi/include.

-- 
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/20170105/17670b03/attachment.html>