bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Thu, 23 Jan 2020 09:17:54 +0000 (09:17 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Thu, 23 Jan 2020 09:17:54 +0000 (09:17 +0000)
commit9624d7c8431a7a09cf2b83b6b17135d3b46381fb
tree437ec1247788bd6bcfba40fa02c8eb7a44f2e559
parent1828f353214da69e98e7a83adf969eb5011a3eb6
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