bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Thu, 16 Jun 2022 10:00:08 +0000 (11:00 +0100)
committerEmilio Pozuelo Monfort <pochu@debian.org>
Thu, 16 Jun 2022 10:00:08 +0000 (11:00 +0100)
commit243f4f75f6a8cead1706e281a5666a0b77468db1
tree0747d22f60aab1574450b3b667e5d92b3fe219eb
parent9ca7185dbaef00c078dec879bb240640afa216a0
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