[llvm-bugs] [Bug 51914] New: Linux::AddClangSystemIncludeArgs() uses wrong paths
via llvm-bugs
llvm-bugs at lists.llvm.org
Mon Sep 20 09:23:49 PDT 2021
https://bugs.llvm.org/show_bug.cgi?id=51914
Bug ID: 51914
Summary: Linux::AddClangSystemIncludeArgs() uses wrong paths
Product: clang
Version: 12.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: libclang
Assignee: unassignedclangbugs at nondot.org
Reporter: christian.morales.vega at gmail.com
CC: klimek at google.com, llvm-bugs at lists.llvm.org,
richard-llvm at metafoo.co.uk
Doxygen doesn't work https://github.com/doxygen/doxygen/issues/8783, apparently
because of https://bugzilla.redhat.com/show_bug.cgi?id=2005620. But it doesn't
seem to be a Fedora-specific issue, but a generic issue that Ubuntu has been
patching for years
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/blob/snapshot/debian/patches/fix-clang-path-and-build.diff.
I could create a Ubuntu-style patch to fix the usage of
clang_parseTranslationUnit() that I need, but it would probably be better to
have a more generic fix upstream.
FWIW this is the CC1Args I have seen after adding a printf to the end of
Linux::AddClangSystemIncludeArgs().
-cc1 -triple x86_64-unknown-linux-gnu -fsyntax-only -disable-free
-main-file-name file.c -mrelocation-model static -mframe-pointer=all
-fallow-editor-placeholders -fmath-errno -fno-rounding-math
-mconstructor-aliases -munwind-tables -target-cpu x86-64 -tune-cpu generic
-fno-split-dwarf-inlining -debugger-tuning=gdb -resource-dir lib64/clang/12.0.1
-internal-isystem /usr/local/include -internal-isystem
lib64/clang/12.0.1/include -internal-externc-isystem /include
-internal-externc-isystem /usr/include
Not sure how the -resource-dir thing works. But if it were "-internal-isystem
/lib64/clang/12.0.1/include" instead of "-internal-isystem
lib64/clang/12.0.1/include" it would already work.
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20210920/31be52cf/attachment.html>
More information about the llvm-bugs
mailing list