bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Mon, 9 May 2022 18:47:26 +0000 (19:47 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Mon, 9 May 2022 18:47:26 +0000 (19:47 +0100)
commit1b6ccfdfaf88daf6ef8cbf2102668ccb60c541d8
tree6ad3f73907057e9a2eab75ce2fdfdd991191c841
parent35700a7611ff887ff74d9a13c89b2afc509108c3
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