bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Wed, 8 Jul 2020 08:49:26 +0000 (09:49 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Wed, 8 Jul 2020 08:49:26 +0000 (09:49 +0100)
commit88f95f8c9cc3d88a7923d7f99a9d25fc064c8938
tree6776a745236c9bb3305dfa4e303a0bb112e3b430
parent1506735d1d1916670820f56a7f217da25a1e4b8d
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