Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can't install two versions of intel-mkl 2019.0.117 #9713

Closed
davydden opened this issue Nov 2, 2018 · 10 comments · Fixed by #11384
Closed

can't install two versions of intel-mkl 2019.0.117 #9713

davydden opened this issue Nov 2, 2018 · 10 comments · Fixed by #11384
Labels

Comments

@davydden
Copy link
Member

davydden commented Nov 2, 2018

Description

seems that intel installer is too clever and picks up the previous installation of intel-mkl using spack. Which is unfortunate as one can't have intel-mkl threads=none and intel-mkl threads=openmp installed at the same time ;-(

Steps to reproduce

spack install intel-mkl
spack install intel-mkl threads=openmp

gives error during installation and prints the message:

The install directory path was changed to <previous-spack-installed-mkl> 
because at least one software product component was detected as having already been installed on the system

Please select at least one component before you continue

Not sure if there is anything Spack can do... ;-(

@jrood-nrel
Copy link
Member

I noticed this as well. Quite frustrating.

@lee218llnl
Copy link
Contributor

You may have to remove the $HOME/intel/.pset directory and/or the $HOME/intel/intel_sdp_products.db file.

@davydden
Copy link
Member Author

davydden commented Nov 6, 2018

@lee218llnl

You may have to remove the $HOME/intel/.pset directory and/or the $HOME/intel/intel_sdp_products.db file.

thanks for the tip. I wonder if we should make it the default behavior in intel packages so that Spack actually supports installation of multiple variants (or at least make it so for intel-mkl)? Or maybe at least mention it in each package description to guide users.

@davydden
Copy link
Member Author

davydden commented Nov 6, 2018

I wonder if we should make it the default behavior in intel packages so that Spack actually supports installation of multiple variants (or at least make it so for intel-mkl)?

@mgsternberg what do you think?

@s-sajid-ali
Copy link
Contributor

I encountered the same issue where I had an older version of intel-mkl which was used to install some packages, but when I tried to install a new version, I got this error :

Checking for older verions :

[sajid@xrmlite ~]$ spack find intel-mkl                                                                                                                        
==> 2 installed packages                                                                                                                                       
-- linux-centos7-x86_64 / gcc@7.3.0 -----------------------------                                                                                              
intel-mkl@2018.3.222                                                                                                                                           
                                                                                                                                                               
-- linux-centos7-x86_64 / intel@18.0.3 --------------------------                                                                                              
intel-mkl@2018.3.222          

Trying to install a new version:

[sajid@xrmlite ~]$ spack install intel-mkl@2019.0.117%intel@18.0.3                                                                                             
==> Installing intel-mkl                                                                                                                                       
==> Searching for binary cache of intel-mkl                                                                                                                    
==> Warning: No Spack mirrors are currently configured                                                                                                         
==> No binary for intel-mkl found: installing from source                                                                                                      
==> Using cached archive: /home/sajid/packages/spack/var/spack/cache/intel-mkl/intel-mkl-2019.0.117.tgz                                                        
==> Staging archive: /home/sajid/packages/spack/var/spack/stage/intel-mkl-2019.0.117-curhdvo35nifojtgv5riil6esclnjg6v/l_mkl_2019.0.117.tgz                     
==> Created stage in /home/sajid/packages/spack/var/spack/stage/intel-mkl-2019.0.117-curhdvo35nifojtgv5riil6esclnjg6v                                          
==> No patches needed for intel-mkl                                                                                                                            
==> Building intel-mkl [IntelPackage]                                                                                                                          
==> Executing phase: 'configure'                                                                                                                               
==> Executing phase: 'install'                                                                                                                                 
==> Error: ProcessError: Command exited with status 2:                                                                                                         
    './install.sh' '--silent' 'silent.cfg'                                                                                                                     
See build log for details:                                                                                                                                     
  /home/sajid/packages/spack/var/spack/stage/intel-mkl-2019.0.117-curhdvo35nifojtgv5riil6esclnjg6v/l_mkl_2019.0.117/spack-build.out                           

Reason for failure:

[sajid@xrmlite ~]$ cat /home/sajid/packages/spack/var/spack/stage/intel-mkl-2019.0.117-curhdvo35nifojtgv5riil6esclnjg6v/l_mkl_2019.0.117/spack-build.out       
==> Executing phase: 'configure'                                                                                                                               
==> Executing phase: 'install'                                                                                                                                 
==> './install.sh' '--silent' 'silent.cfg'                                                                                                                     
--------------------------------------------------------------------------------                                                                               
The install directory path was changed to                                                                                                                      
/home/sajid/packages/spack/opt/spack/linux-centos7-x86_64/intel-18.0.3/intel-mpi                                                                               
-2019.0.117-zukeu5d4z3f4rlnueiwzz2ts44odvawc                                                                                                                   
because at least one software product component was detected as having already                                                                                 
been installed on the system.                                                                                                                                  
--------------------------------------------------------------------------------                                                                               
Please select at least one component before you continue.                                                                                                      
--------------------------------------------------------------------------------                                                                               
                                                                                                                                                               
--------------------------------------------------------------------------------                                                                               

@davydden
Copy link
Member Author

I can confirm that

You may have to remove the $HOME/intel/.pset directory

resolves the problem. I still think there should be some hints for users to do this if such issue appears.

@mforde84
Copy link

I don't have a $HOME/intel directory

@mforde84
Copy link

Ok figured this out.

You need to go to the staging directory and run the interactive version of the installer. When prompted, you need to choose the uninstall option. Once the uninstall is finished, you should be able to reinstall the intel-mkl.

m

@modkin
Copy link
Contributor

modkin commented Apr 10, 2019

So this also means that there is no way of installing e.g. intel-parallel-studio with spack if another version is already manually installed on the system?

We are currently moving to spack and don't want to remove our manual intel installation yet with is located in /software/intel but this does not allow to install intel-parallel-studio in /software/spack due to the error reported above

@davydden
Copy link
Member Author

So this also means that there is no way of installing e.g. intel-parallel-studio with spack if another version is already manually installed on the system?

You can, comment above works for me #9713 (comment)

glennpj added a commit to glennpj/spack that referenced this issue May 7, 2019
- Only return scalapack libraries if `+mpi` is in the spec.
  Fixes spack#11314
  Fixes spack#11289

- set HOME when the intel silent installer is run. This prevents the
  installer from using the ~/intel directory
  Fixes spack#9713
scheibelp pushed a commit that referenced this issue May 10, 2019
Add fixes to support multiple installs and dependents using a subset
of IntelPackage functionality.

* Update IntelPackage to only return scalapack libraries if the root
  spec depends on MPI: scalapack requires MPI to be mentioned as a
  dependency in the DAG. Package builds using intel-mkl for its
  blas/lapack implementations but not for scalapack were failing to
  build.

  Ideally it would be possible to ask if any of the packages in the
  DAG are actually requesting the scalapack functionality provided by
  the IntelPackage and only return scalapack libs in that case, but
  that is not easily done at this time.

  Fixes #11314
  Fixes #11289

* set HOME when the intel silent installer is run. This prevents the
  installer from using the ~/intel directory (which can cause
  conflicts for multiple installs of the same IntelPackage)

  Fixes #9713
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants