bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Fri, 10 Jan 2020 08:37:55 +0000 (08:37 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Fri, 10 Jan 2020 08:37:55 +0000 (08:37 +0000)
commit7af718a1f50b7aca26825eb7092d5d94d9e0da2b
tree105ac643990251cbe4a4e7bb09a1cc77e7260e43
parent9b2afba6b2f03bb4fcb17146e660350b21f6a6be
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