bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Wed, 7 Aug 2019 13:11:36 +0000 (14:11 +0100)
committerGianfranco Costamagna <locutusofborg@debian.org>
Wed, 7 Aug 2019 13:11:36 +0000 (14:11 +0100)
commitcd0d8f3c2f265cb16516ba1b2c1f9a6b10104304
treedabcfc2f1d7a0351018e81c4dff153989c5ac16e
parentbc5536d788f065cc758cd3a3cdf1eb21b3905a5f
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