Known issues: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Below we provide an '''incomplete''' list of known issues. Please mind the description to see whether the issue has been fixed. | Below we provide an '''incomplete''' list of known issues. Please mind the description to see whether the issue has been fixed. | ||
* 2022-02-04: VASP cannot be compiled with the Fujitsu compiler: Fujitsu's Fortran compiler does not support overloaded internal subroutines. First noticed for VASP 6.3.0, will be fixed in VASP 6.3.1. | * 2022-02-04: VASP cannot be compiled with the Fujitsu compiler: Fujitsu's Fortran compiler does not support overloaded internal subroutines. First noticed for VASP 6.3.0, will be fixed in VASP 6.3.1. A simple workaround is to compile without [[:Category:Machine Learning|machine learning capabilities]]. Comment out the macro definition of <code>ML_AVAILABLE</code> in line 626 of <code>src/symbol.inc</code> by adding a <code>!</code> in front, i.e. it should look like this: <code>!#define ML_AVAILABLE</code>. Then do a complete rebuild of VASP: run <code>make veryclean</code> followed by your desired build command. | ||
Revision as of 17:03, 4 February 2022
Below we provide an incomplete list of known issues. Please mind the description to see whether the issue has been fixed.
- 2022-02-04: VASP cannot be compiled with the Fujitsu compiler: Fujitsu's Fortran compiler does not support overloaded internal subroutines. First noticed for VASP 6.3.0, will be fixed in VASP 6.3.1. A simple workaround is to compile without machine learning capabilities. Comment out the macro definition of
ML_AVAILABLEin line 626 ofsrc/symbol.incby adding a!in front, i.e. it should look like this:!#define ML_AVAILABLE. Then do a complete rebuild of VASP: runmake verycleanfollowed by your desired build command.