bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Fri, 18 Sep 2020 09:47:25 +0000 (10:47 +0100)
committerEmilio Pozuelo Monfort <pochu@debian.org>
Fri, 18 Sep 2020 09:47:25 +0000 (10:47 +0100)
commitf0e25bbe98b748bd76d3125a467280cb8d91585e
treee5f1af78625faa6aa34fcb700669e0a31a097213
parent95f7deb14b196747d31db48b105d929f796e58da
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