bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Thu, 28 Feb 2019 12:50:21 +0000 (12:50 +0000)
committerSylvestre Ledru <sylvestre@debian.org>
Thu, 28 Feb 2019 12:50:21 +0000 (12:50 +0000)
commit2ffc8d2c0261e7552a04831a54ddbdaa1301865f
tree941cb65fa4f95d2ad5588e7c419b7f6df5dbc49e
parent89396511a2255a7661a0107c2c6cbbca216149d7
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