From 48a12c8773295f95caa08a77bb660a7ed221995c Mon Sep 17 00:00:00 2001 From: Glenn Johnson Date: Tue, 28 Jan 2020 14:57:06 -0600 Subject: [PATCH] Note about Intel compiler segfault with long paths (#14652) This PR adds a note about segfaults with the Intel compiler when the install paths are long and the dependencies many. --- lib/spack/docs/config_yaml.rst | 20 +++++++++++++++----- 1 file changed, 15 insertions(+), 5 deletions(-) diff --git a/lib/spack/docs/config_yaml.rst b/lib/spack/docs/config_yaml.rst index a64ab27282..865845b274 100644 --- a/lib/spack/docs/config_yaml.rst +++ b/lib/spack/docs/config_yaml.rst @@ -30,11 +30,21 @@ Default is ``$spack/opt/spack``. ``install_hash_length`` and ``install_path_scheme`` --------------------------------------------------- -The default Spack installation path can be very long and can create -problems for scripts with hardcoded shebangs. There are two parameters -to help with that. Firstly, the ``install_hash_length`` parameter can -set the length of the hash in the installation path from 1 to 32. The -default path uses the full 32 characters. +The default Spack installation path can be very long and can create problems +for scripts with hardcoded shebangs. Additionally, when using the Intel +compiler, and if there is also a long list of dependencies, the compiler may +segfault. If you see the following: + + .. code-block:: console + + : internal error: ** The compiler has encountered an unexpected problem. + ** Segmentation violation signal raised. ** + Access violation or stack overflow. Please contact Intel Support for assistance. + +it may be because variables containing dependency specs may be too long. There +are two parameters to help with long path names. Firstly, the +``install_hash_length`` parameter can set the length of the hash in the +installation path from 1 to 32. The default path uses the full 32 characters. Secondly, it is also possible to modify the entire installation scheme. By default Spack uses