Skip to content

Commit

Permalink
Don't make clang use gcc's include-fixed
Browse files Browse the repository at this point in the history
This was breaking `#include_next <limits.h>`, such that we weren't
getting definitions of `PATH_MAX` and `_POSIX_ARG_MAX`.
  • Loading branch information
cuviper committed Aug 22, 2020
1 parent 663d2f5 commit df4bafc
Showing 1 changed file with 0 additions and 9 deletions.
9 changes: 0 additions & 9 deletions src/ci/docker/host-x86_64/dist-x86_64-linux/build-clang.sh
Expand Up @@ -18,16 +18,7 @@ cd clang-build
# For whatever reason the default set of include paths for clang is different
# than that of gcc. As a result we need to manually include our sysroot's
# include path, /rustroot/include, to clang's default include path.
#
# Alsow there's this weird oddity with gcc where there's an 'include-fixed'
# directory that it generates. It turns out [1] that Centos 5's headers are so
# old that they're incompatible with modern C semantics. While gcc automatically
# fixes that clang doesn't account for this. Tell clang to manually include the
# fixed headers so we can successfully compile code later on.
#
# [1]: https://sourceware.org/ml/crossgcc/2008-11/msg00028.html
INC="/rustroot/include"
INC="$INC:/rustroot/lib/gcc/x86_64-unknown-linux-gnu/5.5.0/include-fixed"
INC="$INC:/usr/include"

hide_output \
Expand Down

0 comments on commit df4bafc

Please sign in to comment.