https://bugs.kde.org/show_bug.cgi?id=393779
--- Comment #17 from Milian Wolff <m...@milianw.de> ---
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:
$ ls /usr/lib/clang/6.0.0/include/
adxintrin.h avx512ifmaintrin.h avx512vpopcntdqintrin.h
clzerointrin.h intrin.h pkuintrin.h __stddef_max_align_t.h
__wmmintrin_pclmul.h
altivec.h avx512ifmavlintrin.h avx512vpopcntdqvlintrin.h
cpuid.h inttypes.h pmmintrin.h stdint.h
x86intrin.h
ammintrin.h avx512pfintrin.h avxintrin.h
cuda_wrappers iso646.h popcntintrin.h stdnoreturn.h
xmmintrin.h
arm64intr.h avx512vbmi2intrin.h bmi2intrin.h
emmintrin.h limits.h prfchwintrin.h tbmintrin.h
xopintrin.h
arm_acle.h avx512vbmiintrin.h bmiintrin.h
f16cintrin.h lwpintrin.h rdseedintrin.h tgmath.h
xsavecintrin.h
armintr.h avx512vbmivlintrin.h cetintrin.h
float.h lzcntintrin.h rtmintrin.h tmmintrin.h
xsaveintrin.h
arm_neon.h avx512vlbitalgintrin.h __clang_cuda_builtin_vars.h
fma4intrin.h mm3dnow.h s390intrin.h unwind.h
xsaveoptintrin.h
avx2intrin.h avx512vlbwintrin.h __clang_cuda_cmath.h
fmaintrin.h mmintrin.h shaintrin.h vadefs.h
xsavesintrin.h
avx512bitalgintrin.h avx512vlcdintrin.h __clang_cuda_complex_builtins.h
fxsrintrin.h mm_malloc.h smmintrin.h vaesintrin.h
xtestintrin.h
avx512bwintrin.h avx512vldqintrin.h __clang_cuda_intrinsics.h
gfniintrin.h module.modulemap stdalign.h varargs.h
avx512cdintrin.h avx512vlintrin.h
__clang_cuda_math_forward_declares.h htmintrin.h msa.h
stdarg.h vecintrin.h
avx512dqintrin.h avx512vlvbmi2intrin.h __clang_cuda_runtime_wrapper.h
htmxlintrin.h mwaitxintrin.h stdatomic.h vpclmulqdqintrin.h
avx512erintrin.h avx512vlvnniintrin.h clflushoptintrin.h
ia32intrin.h nmmintrin.h stdbool.h __wmmintrin_aes.h
avx512fintrin.h avx512vnniintrin.h clwbintrin.h
immintrin.h opencl-c.h stddef.h wmmintrin.h
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?
--
You are receiving this mail because:
You are watching all bug changes.
