bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Wed, 4 Dec 2024 12:11:08 +0000 (13:11 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Wed, 4 Dec 2024 12:11:08 +0000 (13:11 +0100)
commit31489b54ca6961973d50b81fd21cb04a12a3709e
tree017b6ccfb5324baec3a59eb8268921a85ef94a54
parent5ce5e94f83e7721aeef4ad446ccc575745d86a72
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