bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sun, 13 Feb 2022 13:04:40 +0000 (13:04 +0000)
committerSylvestre Ledru <sylvestre@debian.org>
Sun, 13 Feb 2022 13:04:40 +0000 (13:04 +0000)
commitbbd1655974a5a63d163c6406916abf95784403a5
tree51b48970eeacb532314d4d0c73815923574da954
parent1d75f4fc71ccf1125ad55b260fc55e0a7fbdd9c0
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