bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 7 Jul 2020 16:18:00 +0000 (17:18 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Tue, 7 Jul 2020 16:18:00 +0000 (17:18 +0100)
commit8d2df044ab0b4c3f5685b3b2fad8ec4692d6810e
treedba9d9dd54a3521095aebc5399824b37d63a6eec
parent0de00de46e55e8deec049bd093f86011956d0ffb
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