bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sat, 23 Jul 2022 21:01:02 +0000 (22:01 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Sat, 23 Jul 2022 21:01:02 +0000 (22:01 +0100)
commitf94bcad5aa7af7704a86b6210ab04da84c3146c2
tree43dab78f76efceff645168ba31074e1c9c8bd6e8
parentd161961b9c86cfc8df222811668354b101050a23
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