https://bugs.kde.org/show_bug.cgi?id=393779
--- Comment #20 from Milian Wolff <m...@milianw.de> --- Yes, I've read your comments. I don't understand why they are contradicting what I said? Clang knows the path to the compiler-builtins, and when you use all of those then sure, the problems will vanish. But only because you are lucky and you used the clang that matches the version of your libclang. This is not necessarily the case. Actually, there are systems where you have libclang but no clang. E.g. on ubuntu: https://packages.ubuntu.com/search?searchon=contents&keywords=varargs.h&mode=exactfilename&suite=artful&arch=any => libclang-common-X.Y-dev Also see https://bugs.kde.org/show_bug.cgi?id=387005#c5 - the version match is important. We will need to find a way to lookup the path that works on all systems. And thinking about it, we shouldn't do it at compile time like we do now, since libclang is usually ABI compatible and if it gets updated without KDevelop being recompiled, things can break again... Sigh, this is such a mess :-/ -- You are receiving this mail because: You are watching all bug changes.
