bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 21 Jul 2020 16:29:06 +0000 (17:29 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Tue, 21 Jul 2020 16:29:06 +0000 (17:29 +0100)
commit622b0659f3baa2f44607c195b578edf6031f35ba
treeeb158bafd8a59065bfa8035056f8765b8ab98cad
parent2b75f5212735988c67eb2e624bd6213fa3a55b2d
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