bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 25 Feb 2020 14:28:58 +0000 (14:28 +0000)
committerGianfranco Costamagna <locutusofborg@debian.org>
Tue, 25 Feb 2020 14:28:58 +0000 (14:28 +0000)
commitde9dfd96ad5d1fcd70242270bb0a20474613dab8
tree042be6e0dab1b51bb0fe5e4dffa922b93aad9507
parent5dc18b667af47c06ff32dd349d1d918b085a9988
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