bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Wed, 2 Jan 2019 11:37:45 +0000 (11:37 +0000)
committerSylvestre Ledru <sylvestre@debian.org>
Wed, 2 Jan 2019 11:37:45 +0000 (11:37 +0000)
commitff63896c97a898959c79e6954c7d1ec4c5145e16
treeb55f82a74ffbfb5c1903571880b26b43c7a6a7e3
parent38c8ad51b39f3d6c4cb09a5c4815f1580dee4236
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