summaryrefslogtreecommitdiff
path: root/var
diff options
context:
space:
mode:
authorAndrew W Elble <aweits@rit.edu>2020-04-21 16:56:50 -0400
committerGitHub <noreply@github.com>2020-04-21 13:56:50 -0700
commitf1050c4be2954db88342f052f24326fb3017b7e0 (patch)
treed58298a49ca9aaea8adac8a2dd4f20a9fb678a01 /var
parent74c159b883ae673710c7a8bcfb1e3543c011152b (diff)
downloadspack-f1050c4be2954db88342f052f24326fb3017b7e0.tar.gz
spack-f1050c4be2954db88342f052f24326fb3017b7e0.tar.bz2
spack-f1050c4be2954db88342f052f24326fb3017b7e0.tar.xz
spack-f1050c4be2954db88342f052f24326fb3017b7e0.zip
compiler wrappers: don't override -isystem with -I (#16077)
If the Spack compiler wrapper encounters any "-isystem" option, then when adding include directories for Spack dependencies, Spack will use "-isystem" instead of "-I". This prevents Spack-generated "-I" options from overriding the "-isystem" options generated by the build system. To ensure that build-system "-isystem" directories are searched first, Spack places all of its inserted "-isystem" directories after. The new ordering of -isystem includes is: * -isystem from build system (not system directories) * -isystem from Spack * -isystem from build system (for directories like /usr/include) The prior order of "-I" arguments is preserved (although as of this commit Spack no longer generates -I if -isystem is detected): * -I from build system (not system directories) * -I from Spack (only if there are no "-isystem" options) * -I from build system (for directories like /usr/include)
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions