Skip to content

Commit df4bafc

Browse files
committed
Don't make clang use gcc's include-fixed
This was breaking `#include_next <limits.h>`, such that we weren't getting definitions of `PATH_MAX` and `_POSIX_ARG_MAX`.
1 parent 663d2f5 commit df4bafc

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

Diff for: src/ci/docker/host-x86_64/dist-x86_64-linux/build-clang.sh

-9
Original file line numberDiff line numberDiff line change
@@ -18,16 +18,7 @@ cd clang-build
1818
# For whatever reason the default set of include paths for clang is different
1919
# than that of gcc. As a result we need to manually include our sysroot's
2020
# include path, /rustroot/include, to clang's default include path.
21-
#
22-
# Alsow there's this weird oddity with gcc where there's an 'include-fixed'
23-
# directory that it generates. It turns out [1] that Centos 5's headers are so
24-
# old that they're incompatible with modern C semantics. While gcc automatically
25-
# fixes that clang doesn't account for this. Tell clang to manually include the
26-
# fixed headers so we can successfully compile code later on.
27-
#
28-
# [1]: https://sourceware.org/ml/crossgcc/2008-11/msg00028.html
2921
INC="/rustroot/include"
30-
INC="$INC:/rustroot/lib/gcc/x86_64-unknown-linux-gnu/5.5.0/include-fixed"
3122
INC="$INC:/usr/include"
3223

3324
hide_output \

0 commit comments

Comments
 (0)