bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Thu, 23 Jan 2020 13:30:57 +0000 (13:30 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Thu, 23 Jan 2020 13:30:57 +0000 (13:30 +0000)
commit1f1403098a65e3c78cc90de48d47c78ceb617858
treea5949c3c009b3b6efb446174a01d0aee4dc33048
parente5293d8e327b8ec12ff2e7116191a6e84bb3bfd4
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