bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sun, 20 Nov 2022 05:54:23 +0000 (05:54 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Sun, 20 Nov 2022 05:54:23 +0000 (05:54 +0000)
commitfb51f66ab45d9de777fcd8af9e893fad7142fa5d
tree5be77ad0b3325f47fb371f6090145551e122d9bd
parent577f64e1a4290d98f9772cfbb29264a4f10cbc75
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