https://bugs.kde.org/show_bug.cgi?id=393779
--- Comment #18 from Eugene Shalygin <eugene.shalygin+bugzilla....@gmail.com> --- (In reply to Milian Wolff from comment #17) > Yes, we have to use paths that fit to whatever libclang you are using. And > libstdc++/libc++ is not important here. This is about the compiler builtin > headers, such as these: Have you seen comments 10 and 11? They seem to directly contradict your statement. > We will have to find a way to cope with your strange libdir. When you query > all the variables in llvm-config, is there any that returns /usr/lib64/? Or > anything we could use to find /usr/lib64/clang/6.0.0/include/varargs.h? $ llvm-config --libdir /usr/lib64/llvm/6/lib64 $ llvm-config --includedir /usr/lib64/llvm/6/include The problem is that the clang include dir contains full version number: /usr/lib64/clang/6.0.0/include -- You are receiving this mail because: You are watching all bug changes.
