-
Notifications
You must be signed in to change notification settings - Fork 5
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
ZEN-27471: PKG/SPEC - sdsc-0.17.3 - Update VASP to support v6.4.x #51
Comments
A number of tickets have come in recently looking for an update to VASP v6.4.2 with Wannier90 integration.
@jerrypgreenberg updated his latest VASP v6.4.x Spack package to support these requests and has run build (and presumably runtime) tests successfully on Expanse. I am deploying the updated |
This is the current
|
Here is the
|
Making a minor change to ensure group permissions are set correctly when deployed.
|
After the updated package has been deployment, here is the new
|
@jerrypgreenberg ran his build (and runtime) tests using an Intel and Intel MPI combo.
However, the existing VASP and Wannier90 deployments already available in expanse/0.17.3/cpu/b use either AOCC or GCC + OpenMPI.
To keep this initial deployment from further expanding the scope of using additional compiler and MPI combinations with VASP and Wannier90, we will attempt to reuse the existing |
The build spec script last ran from the
|
Copying over the GCC version ...
we will modify this spec build script to deploy the VASP v6.4.2 with the Wannier90 integration. |
Initial build launched ...
|
Build failed on problem with the updated Spack package not being able to use Python
|
Yup. It's not being imported for some reason ...
|
Fixed.
|
Let's try that build again now ...
|
Progress. But the build failed again.
It looks like @jerrypgreenberg may have designed the latest version of the package to only work with Intel MKL support to satisfy the BLAS virtual dependency, which will likely preclude reusing the existing copy of Wannier90 available. |
…0.17.3/cpu/b This deployment is in support of recent user requests for VASP v6.4.x compiled with Wannier90 integration [1]. [1] #51
Deployed |
|
Ok
That fpp thing
I forgot about that
I got the same error , searched the Intel compiler installation , found the directory that it's in and added it to my path
Jerry
On Oct 18, 2023, at 5:01 PM, Marty Kandes ***@***.***> wrote:
***@***.*** % ***@***.*** ***@***.*** build is failing.
==> Installing vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6
==> No binary for vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6 found: installing from source
==> Warning: Skipping package at /cm/shared/apps/spack/0.17.3/cpu/b/var/spack/repos/sdsc/packages/amber.configure. "amber.configure" is not a valid Spack module name.
==> Warning: Expected user 527834 to own /scratch/spack_cpu, but it is owned by 0
==> Using cached archive: /cm/shared/apps/spack/0.17.3/cpu/b/var/spack/cache/_source-cache/archive/b7/b704637f7384673f91adfbc803edc5cc7fe736d9623453461f7cdc29b123410e.tgz
==> No patches needed for vasp6
==> Warning: Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors
==> vasp6: Executing phase: 'edit'
==> vasp6: Executing phase: 'build'
==> Error: ProcessError: Command exited with status 2:
'make' 'std' 'gam' 'ncl'
See build log for details:
/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-build-out.txt
==> Error: Terminating after first install failure: ProcessError: Command exited with status 2:
'make' 'std' 'gam' 'ncl'
real 13.53
user 11.44
sys 1.07
==> Warning: Skipping package at /cm/shared/apps/spack/0.17.3/cpu/b/var/spack/repos/sdsc/packages/amber.configure. "amber.configure" is not a valid Spack module name.
==> Regenerating lmod module files
==> OpenFOAM bashrc env: /cm/shared/apps/spack/0.17.3/cpu/b/opt/spack/linux-rocky8-zen2/aocc-3.2.0/openfoam-2106-jz42us227mirxrhqjvojlaut2giuh74j/etc/bashrc
==> vasp6: Executing phase: 'build'
==> [2023-10-18-16:57:59.615141] 'make' 'std' 'gam' 'ncl'
if [ ! -d build/std ] ; then mkdir -p build/std ; fi
cp src/makefile src/.objects src/makedeps.awk makefile.include build/std
make -C build/std VERSION=std check
make[1]: Entering directory '/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-src/build/std'
exit 0
make[1]: Leaving directory '/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-src/build/std'
make -C build/std VERSION=std cleandependencies -j1
make[1]: Entering directory '/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-src/build/std'
rm -f .depend
make[1]: Leaving directory '/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-src/build/std'
make -C build/std VERSION=std all
make[1]: Entering directory '/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-src/build/std'
rsync -ru ../../src/lib .
cp makefile.include lib
make -C lib -j1
make[2]: Entering directory '/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-src/build/std/lib'
make libdmy.a
make[3]: Entering directory '/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-src/build/std/lib'
fpp -f_com=no -free -w0 preclib.F preclib.f90
make[3]: fpp: Command not found
make[3]: *** [makefile:25: preclib.f90] Error 127
make[3]: Leaving directory '/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-src/build/std/lib'
make[2]: *** [makefile:18: all] Error 2
make[2]: Leaving directory '/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-src/build/std/lib'
make[1]: *** [makefile:146: lib] Error 2
make[1]: Leaving directory '/scratch/spack_cpu/job_25752189/spack-stage/spack-stage-vasp6-6.4.2-nfkttoplgemyx6ocwm5osos76s64h4f6/spack-src/build/std'
make: *** [makefile:17: std] Error 2
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/sdsc/spack/issues/51*issuecomment-1769652388__;Iw!!Mih3wA!BFbEGoU540FiRp8ZhsEvrUl4RXFFZ4-qB4_W79dPLwsPm_BfiiD3lttRTnkm-TWGDd7agouL5OuftyyHh4TRgg$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABHQOR65PYO4WQ5BPO27LSTYABUXBAVCNFSM6AAAAAAWETFFMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRZGY2TEMZYHA__;!!Mih3wA!BFbEGoU540FiRp8ZhsEvrUl4RXFFZ4-qB4_W79dPLwsPm_BfiiD3lttRTnkm-TWGDd7agouL5OuftyyUnSbr2Q$>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
….3/cpu/b This deployment is in support of recent user requests for VASP v6.4.x compiled with Wannier90 integration [1]. Please note, however, to satisfy the requests, we have utlized an updated Spack package from @jerrypgreenberg for VASP v6.4.x, which has significant changes to its build process and GPU support --- e.g., moving from CUDA to OpenACC. As such, the Spack package in the sdsc package repo has been update as well, but will not be backwards-compatible with earlier versions of VASP. [1] #51
Build successful. P.S. @jerrypgreenberg - I typically fix these types of issues by explicitly loading the required modules within the spec build script for future documentation/reference. |
No description provided.
The text was updated successfully, but these errors were encountered: