Could you update this call when an fpp-happy version is released so I know that I can install it and revert to the vasp default way of doing things?
Thanks
Search found 3 matches
- Wed Dec 05, 2012 9:24 pm
- Forum: VTSTTools
- Topic: compiling vastcode v3.0b, VASP 5.3.2, Intel v2013.0.079
- Replies: 5
- Views: 18109
- Wed Dec 05, 2012 8:07 pm
- Forum: VTSTTools
- Topic: compiling vastcode v3.0b, VASP 5.3.2, Intel v2013.0.079
- Replies: 5
- Views: 18109
Re: compiling vastcode v3.0b, VASP 5.3.2, Intel v2013.0.079
Reverting to cpp, by commenting out the second CPP line in the Makefile: CPP_ = ./preprocess <$*.F | /usr/bin/cpp -P -C -traditional >$*$(SUFFIX) # this release should be fpp clean # we now recommend fpp as preprocessor # if this fails go back to cpp #bham CPP_=fpp -f_com=no -free -w0 $*.F $*$(SUFFI...
- Tue Dec 04, 2012 2:23 pm
- Forum: VTSTTools
- Topic: compiling vastcode v3.0b, VASP 5.3.2, Intel v2013.0.079
- Replies: 5
- Views: 18109
compiling vastcode v3.0b, VASP 5.3.2, Intel v2013.0.079
The make for VASP with vastcode v3.0b, VASP 5.3.2, Intel v2013.0.079 gives warnings: mpif90 -free -names lowercase -assume byterecl -O2 -ip -c dimer.f90 dimer.F(79): warning #5117: Bad # preprocessor line #if defined(MPI_CHAIN) ------^ dimer.F(82): warning #5117: Bad # preprocessor line #endif -----...