You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now when started not from system path like /bin or /usr/bin, the tool argues that it cannot locate include files stddef.h, stdint.h etc. when parsing system headers like <iostream>. This of course causes mayhem and incorrect behavior.
the default location to look for builtin headers is in a path $(dirname /path/to/tool)/../lib/clang/3.3/include relative to the tool binary. This works out-of-the-box for tools running from llvm’s toplevel binary directory after building clang-headers, or if the tool is running from the binary directory of a clang install next to the clang binary.
Berkus Decker, [15.03.18 11:09]
it is not /usr/bin, it is clang-install-dir wherever you've installed it, it is considered as root, since that's the way relocatable toolchain is done in LLVM
Right now when started not from system path like
/bin
or/usr/bin
, the tool argues that it cannot locate include filesstddef.h
,stdint.h
etc. when parsing system headers like<iostream>
. This of course causes mayhem and incorrect behavior.The issue is related to clang builtin includes. To quote:
Another clue from pro.cxx
Another clue.
Once fixed, apply the same to leak-marker.
The text was updated successfully, but these errors were encountered: