bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Fri, 22 Jul 2022 13:10:20 +0000 (14:10 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Fri, 22 Jul 2022 13:10:20 +0000 (14:10 +0100)
commit9e989551b686af4bb2894cf6088fe0bbc9f5e240
tree12ac150fee20f2841393fcceb74077435ff8241d
parent29098ee66a5c2ee18982238bdfbfba917949c3dc
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h