bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Fri, 10 Apr 2020 08:27:41 +0000 (09:27 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Fri, 10 Apr 2020 08:27:41 +0000 (09:27 +0100)
commit95623cf34885e394b1e88e747bc7dea4d5de35a1
tree8a40d51a5e8fcef452a6c4d05155950e8d5706ea
parent4b22d5360de7cf8bb07ecee378cf948a55236176
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