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
Comments
I noticed this as well. Quite frustrating. |
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 |
@mgsternberg what do you think? |
I encountered the same issue where I had an older version of Checking for older verions :
Trying to install a new version:
Reason for failure:
|
I can confirm that
resolves the problem. I still think there should be some hints for users to do this if such issue appears. |
I don't have a $HOME/intel directory |
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 |
So this also means that there is no way of installing e.g. We are currently moving to spack and don't want to remove our manual intel installation yet with is located in |
You can, comment above works for me #9713 (comment) |
- 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
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
Description
seems that intel installer is too clever and picks up the previous installation of
intel-mkl
usingspack
. Which is unfortunate as one can't haveintel-mkl threads=none
andintel-mkl threads=openmp
installed at the same time ;-(Steps to reproduce
gives error during installation and prints the message:
Not sure if there is anything Spack can do... ;-(
The text was updated successfully, but these errors were encountered: