bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 12 Nov 2019 13:12:48 +0000 (13:12 +0000)
committerSylvestre Ledru <sylvestre@debian.org>
Tue, 12 Nov 2019 13:12:48 +0000 (13:12 +0000)
commite3b6e6db5ec6f110a10b6e35b0e55b008e4bbc08
tree9d865a676207fa5dab441d18f9c854d2032095ef
parent1979c0ce63ddf2ef06bf7a5af581be4daf67173b
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