[Pw_forum] Setup problems with espresso-3.2 Attn. Prof. Giannozzi

[Amos Leffler]

Dear Prof. Giannozzi,
	My original message was returned because it was too long and I removed most of 
it.  
	I used the configure command:
   ./configure MIF=g95 FFLAGS="-O2 -assume byterecl"
and it didn't work.  However " ./configure" does work correctly.  I should have mentioned 
that I used the intel MKL/8.1 library and this worked for LAPACK LIBS 
and BLAS LIBS but not for FFT where the internal FFTW file was used.
   
       When I used "make all"  the compilation used "g95" even though it 
was not mentioned.  It gave two errors as follows:

bp_radin.f: undefined reference to `s_wsle'
libpw.a(bp_radin.o)(.text+0x181):bp_radin.f: undefined reference to `do_lio'
libpw.a(bp_radin.o)(.text+0x189):bp_radin.f: undefined reference to `e_wsle'
libpw.a(bp_radin.o)(.text+0x196):bp_radin.f: undefined reference to `s_wsle'
libpw.a(bp_radin.o)(.text+0x1ac):bp_radin.f: undefined reference to `do_lio'
libpw.a(bp_radin.o)(.text+0x1c4):bp_radin.f: undefined reference to `do_lio'
libpw.a(bp_radin.o)(.text+0x1c9):bp_radin.f: undefined reference to `e_wsle'
libpw.a(bp_radin.o)(.text+0x1d7):bp_radin.f: undefined reference to `s_stop'
libpw.a(bp_radin.o)(.text+0x2b7): In function `radlg1_':
bp_radin.f: undefined reference to `s_wsle'
libpw.a(bp_radin.o)(.text+0x2cd):bp_radin.f: undefined reference to `do_lio'
libpw.a(bp_radin.o)(.text+0x2d5):bp_radin.f: undefined reference to `e_wsle'
libpw.a(bp_radin.o)(.text+0x2e2):bp_radin.f: undefined reference to `s_wsle'
libpw.a(bp_radin.o)(.text+0x2f8):bp_radin.f: undefined reference to `do_lio'
libpw.a(bp_radin.o)(.text+0x310):bp_radin.f: undefined reference to `do_lio'
libpw.a(bp_radin.o)(.text+0x315):bp_radin.f: undefined reference to `e_wsle'
libpw.a(bp_radin.o)(.text+0x323):bp_radin.f: undefined reference to `s_stop'
make[1]: *** [pw.x] Error 1
make[1]: Leaving directory `/home/amos3/Desktop/espresso-3.2/PW'
make: *** [pw] Error 2

	I looked at the PW directory list and noted that bp_radin.f and by_ylm_q.f are the only two files that have a ".f" extension.  Also there is bp.mod which has no extension.  Could these be the trouble? 

The entire configure file was attached to the e-mail and I removed this except to note that it gave the final statement as:
                            configure: exit 0                                                                                             
so it appears that the configure went OK.
								Amos Leffler