bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sat, 14 Oct 2023 16:37:48 +0000 (17:37 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Sat, 14 Oct 2023 16:37:48 +0000 (17:37 +0100)
commit9f8beadd5cbe00ac0640ab50e1d574d604b9281c
treee7fa5fcecc25827dafb2cad0624d5290d3353a64
parent210cd864e8330575e698d58ecb0096d1a5ad4902
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