bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 25 Feb 2020 14:08:36 +0000 (14:08 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Tue, 25 Feb 2020 14:08:36 +0000 (14:08 +0000)
commit511820693aca1539c8038e819bff78b88589409d
tree9c51579977f80da0a258fc8aa0d079330ddfb442
parent6c255d4540ecb8b146bb0b4db2910c9cf6dcb6e7
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