bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sat, 11 Jun 2022 07:09:03 +0000 (08:09 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Sat, 11 Jun 2022 07:09:03 +0000 (08:09 +0100)
commit4f617202a69d80b0348994de5e5c548c4f0a754b
tree00560b1fb671b1d734a361d0fbd928e622090c01
parent57cc74b28f79c7baf2f96310397a7f1e792d21d0
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