[Wien] Compiling WIEN2k21: error with findloc in lapw0_mpi

2021-04-15 Thread pboulet
Hello, It seems there is a problem with findloc in lapw0_mpi. The program does not compile. The error message is: SRC_lapw0/compile.msg:lapw0.F(2370): error #6404: This name does not have a type, and must have an explicit type. [FINDLOC] I am using intel fortran compiler( v. 17), with

Re: [Wien] Compiling WIEN2k21: error with findloc in lapw0_mpi

2021-04-15 Thread Peter Blaha
|FINDLOC| — Search an array for a value is a standard Fortran function (2008 standard). It is available in gfortran (at least in version 10) and also in newer ifort versions. It could be that your ifort v17 does not support it yet. I suggest to upgrade to the new intel

[Wien] bug report: WIEN2k-21.1 : lapw1para_lapw

2021-04-15 Thread Takashi Nemoto
Dear sirs, At first, I am grad to get a new release of WIEN2k. By the way, I found a small bug on script "lapw1para_lapw". The check of local directory seems wrong. "./" is usually NFS shared directory, so I think "!=" should be "==". if($?SCRATCH) then if($SCRATCH != "./" ) then

Re: [Wien] bug report: WIEN2k-21.1 : lapw1para_lapw

2021-04-15 Thread Takashi Nemoto
Dear Blaha Thank you for answering. I just understand the logic of script. So, in case directory (shared "./"), we can set the granularity freely. And in the case of (remote) local directory, granularity should be 1. I misunderstood the "nonlocal SCRATCH". Also, I know that the second problem

Re: [Wien] bug report: WIEN2k-21.1 : lapw1para_lapw

2021-04-15 Thread Peter Blaha
Hi, Thanks for the report, but I don't think that these are bugs with WIEN2k: By the way, I found a small bug on script "lapw1para_lapw". The check of local directory seems wrong. "./" is usually NFS shared directory, so I think "!=" should be "==". if($?SCRATCH) then

Re: [Wien] bug report: WIEN2k-21.1 : lapw1para_lapw

2021-04-15 Thread Peter Blaha
Thank you for answering. I just understand the logic of script. So, in case directory (shared "./"), we can set the granularity freely. And in the case of (remote) local directory, granularity should be 1. Exactly. Also, I know that the second problem comes from Ubuntu Linux, but, for me,

Re: [Wien] bug report: WIEN2k-21.1 : lapw1para_lapw

2021-04-15 Thread Gavin Abo
I don't think that is a Ubuntu bug.  It seemed to be intended behavior for many Linux distributions as some programs don't safely run in non-interactive mode as explained better in the reference [5] in the post at: https://www.mail-archive.com/wien@zeus.theochem.tuwien.ac.at/msg18685.html On

Re: [Wien] bug report: WIEN2k-21.1 : lapw1para_lapw

2021-04-15 Thread Laurence Marks
The default .bashrc file is set either by the OS, or by a sysadmin depending upon whether you downloaded Ubuntu or you are using a shared system. It is meant to be edited. If it is a shared system then you should talk to the sysadmin; maybe there was a reason. If it is your personal computer is