summaryrefslogtreecommitdiff
path: root/bin/spack_pwsh.ps1
diff options
context:
space:
mode:
authorHarmen Stoppels <harmenstoppels@gmail.com>2022-07-22 15:11:38 +0200
committerGitHub <noreply@github.com>2022-07-22 15:11:38 +0200
commit799553d302a16804d541524b6f56b5b2adef891d (patch)
treeddf519b1f1b5914b85a026e9e6b8a97eee27797f /bin/spack_pwsh.ps1
parent5cf7bf37701a18d73730f05894d0f81dff16493e (diff)
downloadspack-799553d302a16804d541524b6f56b5b2adef891d.tar.gz
spack-799553d302a16804d541524b6f56b5b2adef891d.tar.bz2
spack-799553d302a16804d541524b6f56b5b2adef891d.tar.xz
spack-799553d302a16804d541524b6f56b5b2adef891d.zip
autotools: add -I flag when non-standard libtool (#31677)
When 1. Spack installs libtool, 2. system libtool is installed too, and 3. system automake is used Spack passes system automake's `-I <prefix>` flag to itself, even though it's a default search path. This takes precedence over spack's libtool prefix dir. This causes the wrong `libtool.m4` file to be used (since system libtool is in the same prefix as system automake). And that leads to error messages about incompatible libtool, something something LT_INIT.
Diffstat (limited to 'bin/spack_pwsh.ps1')
0 files changed, 0 insertions, 0 deletions