[llvm-bugs] [Bug 33607] New: Clang libtools built out-of-tree cannot find libc++ on MacOS

[via llvm-bugs]

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

            Bug ID: 33607
           Summary: Clang libtools built out-of-tree cannot find libc++ on
                    MacOS
           Product: clang
           Version: 4.0
          Hardware: All
                OS: MacOS X
            Status: NEW
          Severity: normal
          Priority: P
         Component: Frontend
          Assignee: unassignedclangbugs at nondot.org
          Reporter: sdconsta at syr.edu
                CC: llvm-bugs at lists.llvm.org

Until OS X 10.9, libc++ headers were installed into /usr/include/c++/v1. Since
then, then have been installed either as part of the XCode.app library, or as
part of the XCode command line tools. So they could potentially be in the
following locations:

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1
/Library/Developer/CommandLineTools/usr/include/c++/v1

In InitHeaderSearch.cpp (here:
https://clang.llvm.org/doxygen/InitHeaderSearch_8cpp_source.html),
InitHeaderSearch::AddDefaultIncludePaths() still uses /usr/include/c++/v1. This
doesn't matter for clang itself, because it can always find libc++ through the
relative path ../include/c++/v1. The problem arises when a libtool is built
out-of-tree using the clang Frontend library. In this case, on OS X 10.9+,
neither the legacy path (/usr/include/c++/v1) nor the relative path used by
clang will work.

Here is the relevant cfe-dev thread on this topic:

http://lists.llvm.org/pipermail/cfe-dev/2017-June/054425.html

-- 
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/20170627/a81f44f5/attachment.html>