bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Tue, 14 Jan 2025 13:16:47 +0000 (14:16 +0100)
commit9a2010d19f058ed7521a3ebd612c9c5f3aa8f960
tree66fb481ae4fe622071c0476876ccbc5a4c4cecbd
parent710b5416a97180a6b218712b58ebd23e40b23c87
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