summaryrefslogtreecommitdiff
path: root/var
diff options
context:
space:
mode:
authorbernhardkaindl <43588962+bernhardkaindl@users.noreply.github.com>2021-09-08 12:09:07 +0200
committerGitHub <noreply@github.com>2021-09-08 12:09:07 +0200
commit4e4b199f1693ea9df95af2421b1ebbe2f808abd3 (patch)
tree76f6d91a23d06afc409603278728ab838c441095 /var
parent0fb5a39c17e5be20595a2f11690815cf247fe4a6 (diff)
downloadspack-4e4b199f1693ea9df95af2421b1ebbe2f808abd3.tar.gz
spack-4e4b199f1693ea9df95af2421b1ebbe2f808abd3.tar.bz2
spack-4e4b199f1693ea9df95af2421b1ebbe2f808abd3.tar.xz
spack-4e4b199f1693ea9df95af2421b1ebbe2f808abd3.zip
lib/spack/env/cc: tolerate trailing / in elements of $PATH (#25733)
Fixes removal of SPACK_ENV_PATH from PATH in the presence of trailing slashes in the elements of PATH: The compiler wrapper has to ensure that it is not called nested like it would happen when gcc's collect2 uses PATH to call the linker ld, or else the compilation fails. To prevent nested calls, the compiler wrapper removes the elements of SPACK_ENV_PATH from PATH. Sadly, the autotest framework appends a slash to each element of PATH when adding AUTOTEST_PATH to the PATH for the tests, and some tests like those of GNU bison run cc inside the test. Thus, ensure that PATH cleanup works even with trailing slashes. This fixes the autotest suite of bison, compiling hundreds of bison-generated test cases in a autotest-generated testsuite. Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions