bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Thu, 22 Oct 2020 20:29:07 +0000 (21:29 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Thu, 22 Oct 2020 20:29:07 +0000 (21:29 +0100)
commitae4c969ec94703988cb0bda8fa1c75f8214e9947
tree94afff8b99c9ddbea603785170275896869b71b9
parent53c026612e9aa02bfdeaed029b5fdbe9f616b80d
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