bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 9 Jul 2019 19:04:39 +0000 (20:04 +0100)
committerPeter Michael Green <plugwash@raspbian.org>
Tue, 9 Jul 2019 19:04:39 +0000 (20:04 +0100)
commit187cc4537acb36186a6f11d1fb15f5bf616e27ac
treee39aad4a752b8d4d1a0cc509553fcbb399725c86
parent9442b66cbe747df4cb5f6c1e57f3ff2fd3c54a39
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