Summary: | llvm-core/clang doesn't show the same behaviour of libclang | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fabio Rossi <rossi.f> |
Component: | Current packages | Assignee: | LLVM support project <llvm> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | herrtimson, negril.nx+gentoo, parona, rossi.f, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=811723 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Fabio Rossi
2024-04-05 22:25:15 UTC
Ah, I wonder if this explains bug 811723... It partly does, as in that both are the result of failed resource dir lookup. Causes are different though. You will need to pass: '-resource-dir', '${LLVM_ROOT}' e.g '-resource-dir', '/usr/lib/clang/18' in args, clang does this for calls to clang on it's own. Changing that is really up to upstream imho. Added bonus that if you are less than 5 levels deep, "../../../../lib/clang/17/include" will resolve to "lib/clang/17/include", and that is symlinked to "/usr/lib" on merged-usr. |