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

2019-06-25 Thread Fecher, Gerhard
Dear Gavin, Sorry my question was probably to short, it should read Does anyone know whether "== " works with gfortran ? With ifort the following test works well, but I cannot test it with gfortran The answer in the Intel forum that you quote does not include "==" program logicaltest

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

2019-06-25 Thread Gavin Abo
The == should work for C/C++ language.  I don't recall ever seeing that being used for Fortran. A quote from a HP Doctor Fortran article [ https://software.intel.com/en-us/forums/intel-visual-fortran-compiler-for-windows/topic/274462 ]: "The real trouble with making assumptions about the

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

2019-06-25 Thread Mikhail Nestoklon
Thank you. LAPW1 seem to work with default 4 threads. Now run_lapw stops at the next step:  STOP LAPW0 END STOP LAPW1 END STOP LAPW2 - Error. Check file lapw2.error $ cat lapw2.error 'LAPW2' - can't open unit: 15 'LAPW2' - filename: GaAs.tmp 'LAPW2' - status: scratch form: unformatted In the

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

2019-06-25 Thread Fecher, Gerhard
Does == work ? Ciao Gerhard DEEP THOUGHT in D. Adams; Hitchhikers Guide to the Galaxy: "I think the problem, to be quite honest with you, is that you have never actually known what the question is." Dr. Gerhard H. Fecher Institut of Inorganic and Analytical

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

2019-06-25 Thread Sam Trickey
See below On 6/25/19 5:47 AM, Peter Blaha wrote: Hi, I can confirm the fix for   inputpars.F.   Of course, according to fortran standards a logical if should have an .eqv. operator (although I never "understood" what that should be good for ...). Keeps computer scientists occupied

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

2019-06-25 Thread Peter Blaha
Hi, I can confirm the fix for inputpars.F. Of course, according to fortran standards a logical if should have an .eqv. operator (although I never "understood" what that should be good for ...). Also your second problem I have most likely recently seen myself. I guess it happens only