bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sun, 4 Dec 2022 08:03:06 +0000 (08:03 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Sun, 4 Dec 2022 08:03:06 +0000 (08:03 +0000)
commit17e05d378874a6dfe06747150c7e134fb5bded03
treef407065e6697928828eb15481475681475c06ad0
parentf50be1ef474928f4a23b299cbd32f816080ed28f
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