bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 31 Mar 2020 19:11:56 +0000 (20:11 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Tue, 31 Mar 2020 19:11:56 +0000 (20:11 +0100)
commit43eebd18d2208ab85403cc77a88c101b2ffe7480
tree7426f629e121a1ed2d446818997b8a2556f0f28b
parent9d12685a25d98b4455ca50e28bb8ac1c584d8ad5
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