You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Command ssh fails in an activated ChronoLog Spack environment.
Steps to reproduce
Run ssh localhost after activating ChronoLog Spack environment using spack env activate -p . in the root directory of the repo.
What is the current bug behavior?
ssh fails with an error message like OpenSSL version mismatch. Built against 30000020, you have 30100030.
What is the expected correct behavior?
ssh should work normally as usual. No error message of mismatched OpenSSL version should pop up.
Potential solution
Spack should support forcing to use existing packages from the system unless it breaks the compatibility. The root package of this issue is probably cmake which depends on curl which uses openssl. Adding proper options to configure cmake to use system's packages should fix this.
The text was updated successfully, but these errors were encountered:
Summary
Command
ssh
fails in an activated ChronoLog Spack environment.Steps to reproduce
Run
ssh localhost
after activating ChronoLog Spack environment usingspack env activate -p .
in the root directory of the repo.What is the current bug behavior?
ssh
fails with an error message likeOpenSSL version mismatch. Built against 30000020, you have 30100030
.What is the expected correct behavior?
ssh
should work normally as usual. No error message of mismatched OpenSSL version should pop up.Potential solution
Spack should support forcing to use existing packages from the system unless it breaks the compatibility. The root package of this issue is probably
cmake
which depends oncurl
which usesopenssl
. Adding proper options to configurecmake
to use system's packages should fix this.The text was updated successfully, but these errors were encountered: