bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Fri, 4 Nov 2022 18:36:56 +0000 (18:36 +0000)
committerSylvestre Ledru <sylvestre@debian.org>
Fri, 4 Nov 2022 18:36:56 +0000 (18:36 +0000)
commit6b6fa6644768bd50c47b124c8a9c0c3253615dc7
tree3e12e8c3917b81152b3c879fbbae56f3a4f68ff4
parente63dfbde986550080da6574598c786a63cef803b
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