bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sat, 5 Apr 2025 20:24:44 +0000 (22:24 +0200)
committerSylvestre Ledru <sylvestre@debian.org>
Sat, 5 Apr 2025 20:24:44 +0000 (22:24 +0200)
commitb76832136ab5292c6384433af97bae379a602b60
treedb20684896ae99229804bdb39bea1850d81cfb91
parent152d59bf4ed1c07226a2084c917c9d87dca07adc
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