bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Wed, 2 Sep 2020 11:55:46 +0000 (12:55 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Wed, 2 Sep 2020 11:55:46 +0000 (12:55 +0100)
commit8b14001ce12263644145f08a0325f142415bec13
treeb3ad7864c46bd3cec8c6dde9ff8da1deb828f046
parentae4193913e8643afa3559ce656c7c5b093a1ab66
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