Re: [Wien] gfortran compilation and run problems for 19.1

2019-06-26 Thread Peter Blaha
I can confirm the lapw2 problem with gfortran. According to the Fortran standard, you can specify status=scratch, but then you MUST NOT specify a "FILE=...". (ifort can handle this easily). You can edit x_lapw and remove the line with unit 15 in the lapw2: section (search for lapw2:, then

Re: [Wien] gfortran compilation and run problems for 19.1

2019-06-26 Thread Gavin Abo
Interesting, it does compile and run with ifort but does not compile with gfortran.  The -stand option could be used with ifort so that it gives a compiler message similar to gfortran [ https://software.intel.com/en-us/fortran-compiler-developer-guide-and-reference-stand ]:

Re: [Wien] gfortran compilation and run problems for 19.1

2019-06-26 Thread Mikhail Nestoklon
No, it understands the intention of the person who wrote the code but this is an error. @ gfortran 7.4.0 if(a == b) then 1 Error: Logicals at (1) must be compared with .eqv. instead of == gfort_test.f:15:9: if(a .eq. b) then 1 Error: Logicals at (1) must be compared with .eqv. instead of .eq.