bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Mon, 30 Dec 2019 14:31:05 +0000 (14:31 +0000)
committerPeter Michael Green <plugwash@raspbian.org>
Mon, 30 Dec 2019 14:31:05 +0000 (14:31 +0000)
commit3bcd4ebafafe420ed8ba1c92b9be4c3b046d7827
tree1e615dcf14ee2edaa633fbba2357071647bc44af
parent651a27d55bc150ed69613069325a141e2ec4bfa5
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