bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sun, 21 Apr 2019 20:55:47 +0000 (21:55 +0100)
committerGianfranco Costamagna <locutusofborg@debian.org>
Sun, 21 Apr 2019 20:55:47 +0000 (21:55 +0100)
commit6bc599a50f456af14e16815ae0876d8e40b3c930
tree52a5341cb5b911a8f9643cee76ef8efc98ad3219
parent209d3377469a8a3d0eedc43c1072646c0b79ca6b
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