[Pw_forum] Installation problem on Intel i32 ubuntu

ZEYAD ALAHMED zalahmed at hotmail.com
Mon Nov 26 21:47:12 CET 2007


Dear pwscf users,
  I have been trying to install the code "espresso-3.2.3" on my computer (Intel i32 - Ubuntu).
I have Intel compilers (ifort 10.1.008),  (icc 10.1.008), and mkl lib ( 10.0.011 ). 
When I issue ./configure , every things are OK. (configure: success).
However, when I run (make all) I allways get the same problem : 

.
.
.
es/wave_base.o ../Modules/xml_io_base.o libpw.a ../flib/ptools.a ../flib/flib.a ../clib/clib.a ../iotk/src/libiotk.a -lmkl_lapack -L/opt/intel/mkl/10.0.011/lib/32 -lmkl_ia32 -lguide -lpthread -lfftw
/opt/intel/mkl/10.0.011/lib/32/libmkl_lapack.so: undefined reference to `mkl_serv_load_fun'
/opt/intel/mkl/10.0.011/lib/32/libmkl_lapack.so: undefined reference to `mkl_serv_load_dll'
make[1]: *** [pw.x] Error 1
make[1]: Leaving directory `/home/A/espresso-3.2.3/PW'
make: *** [pw] Error 2


What is wrong and any suggestions!


Thanks for help in advance


Zeyad Alahmed, PhD 
College of Science, King Saud University 
 zalahmed at hotmail.com






Here are make.sys and config.long files:
-------------------------
############
make.sys
############

# make.sys.  Generated from make.sys.in by configure.

# compilation rules

.SUFFIXES :
.SUFFIXES : .o .c .f .f90

# most fortran compilers can directly preprocess c-like directives: use
#       $(MPIF90) $(F90FLAGS) -c $<
# if explicit preprocessing by the C preprocessor is needed, use:
#       $(CPP) $(CPPFLAGS) $< -o $*.F90
#       $(MPIF90) $(F90FLAGS) -c $*.F90 -o $*.o
# remember the tabulator in the first column !!!

.f90.o:
        $(MPIF90) $(F90FLAGS) -c $<

# .f.o and .c.o: do not modify

.f.o:
        $(F77) $(FFLAGS) -c $<

.c.o:
        $(CC) $(CFLAGS)  -c $<


# DFLAGS  = precompilation options (possible arguments to -D and -U)
#           used by the C compiler and preprocessor
# FDFLAGS = as DFLAGS, for the f90 compiler
# See include/defs.h.README for a list of options and their meaning
# With the exception of IBM xlf, FDFLAGS = $(DFLAGS)
# For IBM xlf, FDFLAGS is the same as DFLAGS with separating commas

DFLAGS         =  -D__INTEL -D__FFTW
FDFLAGS        = $(DFLAGS)

# IFLAGS = how to locate directories where files to be included are
# In most cases, IFLAGS = -I../include
# If loading an external FFTW library, add the location of FFTW include files

IFLAGS         = -I../include  -lfftw

# MODFLAGS = flag used by f90 compiler to locate modules
# You need to search for modules in ./, in ../iotk/src, in ../Modules
# Some applications also neeed modules in ../PW, ../PH, ../CPV

MODFLAGS       = -I./  -I../Modules  -I../iotk/src \
                 -I../PW  -I../PH  -I../CPV

# Compilers: fortran-90, fortran-77, C
# If a parallel compilation is desired, MPIF90 should be a fortran-90
# compiler that produces executables for parallel execution using MPI
# (such as for instance mpif90, mpf90, mpxlf90,...);
# otherwise, an ordinary fortran-90 compiler (f90, g95, xlf90, ifort,...)
# If you have a parallel machine but no suitable candidate for MPIF90,
# try to specify the directory containing "mpif.h" in IFLAGS
# and to specify the location of MPI libraries in MPI_LIBS

MPIF90         = ifort
#F90           = ifort
CC             = icc
F77            = ifort

# C preprocessor and preprocessing flags - for explicit preprocessing,
# if needed (see the compilation rules above)
# preprocessing flags must include DFLAGS and IFLAGS

CPP            = cpp
CPPFLAGS       = -P -traditional $(DFLAGS) $(IFLAGS)

# compiler flags: C, F90, F77
# C flags must include DFLAGS and IFLAGS
# F90 flags must include MODFLAGS, IFLAGS, and FDFLAGS with appropriate syntax

CFLAGS         = -O3 $(DFLAGS) $(IFLAGS)
F90FLAGS       = $(FFLAGS) -nomodule -fpp $(FDFLAGS) $(IFLAGS) $(MODFLAGS)
FFLAGS         = -O2 -assume byterecl

# compiler flags without optimization for fortran-77
# the latter is NEEDED to properly compile dlamch.f, used by lapack

FFLAGS_NOOPT   = -O0 -assume byterecl

# Linker and linker-specific flags (if any)
# Typically LD coincides with F90 or MPIF90

LD             = ifort
LDFLAGS        =

# External Libraries (if any) : blas, lapack, fft, MPI

# If you have nothing better, use the local copy : ../flib/blas.a

BLAS_LIBS      = -L/opt/intel/mkl/10.0.011/lib/32 -lmkl_ia32 -lguide -lpthread

# The following lapack libraries will be available in flib/ :
# ../flib/lapack.a : contains all needed routines
# ../flib/lapack_atlas.a: only routines not present in the Atlas library
# For IBM machines with essl: load essl BEFORE lapack !
# remember that LAPACK_LIBS precedes BLAS_LIBS in loading order

LAPACK_LIBS    = -lmkl_lapack

# nothing needed here if the the internal copy of FFTW is compiled
# (needs -D__FFTW -D__USE_INTERNAL_FFTW in DFLAGS)

FFT_LIBS       =  -lfftw

# For parallel execution, the correct path to MPI libraries must
# be specified in MPI_LIBS (except for IBM if you use mpxlf)

MPI_LIBS       =

# IBM-specific: MASS libraries, if available and if -D__MASS is defined in FDFLAGS

MASS_LIBS      =

# pgplot libraries (used by some post-processing tools)

PGPLOT_LIBS    =

# ar command and flags - for most architectures: AR = ar, ARFLAGS = ruv
# ARFLAGS_DYNAMICS is used in iotk to produce a dynamical library,
# for Mac OS-X with PowerPC and xlf compiler. In all other cases
# ARFLAGS_DYNAMICS = $(ARFLAGS)

AR             = ar
ARFLAGS        = ruv
ARFLAGS_DYNAMIC= ruv

# ranlib command. If ranlib is not needed (it isn't in most cases) use
# RANLIB = echo

RANLIB         = ranlib

# all internal and external libraries - do not modify

LIBOBJS        = ../flib/ptools.a ../flib/flib.a ../clib/clib.a ../iotk/src/libiotk.a
LIBS           = $(LAPACK_LIBS) $(BLAS_LIBS) $(FFT_LIBS) $(MPI_LIBS) $(MASS_LIBS) $(PGPLOT_LIBS)
-----------------------------


##############
config.log:
##############



This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by ESPRESSO configure 3.2, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ ./configure

## --------- ##
## Platform. ##
## --------- ##

hostname = ubuntu-laptop
uname -m = i686
uname -r = 2.6.15-29-386
uname -s = Linux
uname -v = #1 PREEMPT Mon Sep 24 17:18:25 UTC 2007

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = i686
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
hostinfo               = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /opt/intel/idb/10.1.008/bin
PATH: /opt/intel/cc/10.1.008/bin
PATH: /opt/intel/fc/10.1.008/bin
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/bin/X11
PATH: /usr/games
PATH: /home/zeyad/.local/bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1395: checking build system type
configure:1413: result: i686-pc-linux-gnu
configure:1598: checking for ifort
configure:1614: found /opt/intel/fc/10.1.008/bin/ifort
configure:1624: result: ifort
configure:1639: checking for Fortran 77 compiler version
configure:1642: ifort --version &5
ifort (IFORT) 10.1 20070913
Copyright (C) 1985-2007 Intel Corporation.  All rights reserved.

configure:1645: $? = 0
configure:1647: ifort -v &5
Version 10.1
configure:1650: $? = 0
configure:1652: ifort -V &5
Intel(R) Fortran Compiler for applications running on IA-32, Version 10.1    Build 20070913 Package ID: l_fc_p_10.1.008
Copyright (C) 1985-2007 Intel Corporation.  All rights reserved.
FOR NON-COMMERCIAL USE ONLY

configure:1655: $? = 0
configure:1669: checking for Fortran 77 compiler default output file name
configure:1672: ifort   conftest.f >&5
configure:1675: $? = 0
configure:1721: result: a.out
configure:1726: checking whether the Fortran 77 compiler works
configure:1752: result: yes
configure:1759: checking whether we are cross compiling
configure:1761: result: yes
configure:1764: checking for suffix of executables
configure:1766: ifort -o conftest   conftest.f >&5
configure:1769: $? = 0
configure:1794: result:
configure:1800: checking for suffix of object files
configure:1811: ifort -c  conftest.f>&5
configure:1814: $? = 0
configure:1836: result: o
configure:1844: checking whether we are using the GNU Fortran 77 compiler
configure:1858: ifort -c  conftest.F>&5
fortcom: Error: conftest.F, line 3: Syntax error, found END-OF-STATEMENT when expecting one of: => = . ( : %
       choke me
---------------^
fortcom: Error: conftest.F, line 3: This statement is positioned incorrectly and/or has syntax errors.
       choke me
---------------^
compilation aborted for conftest.F (code 1)
configure:1864: $? = 1
configure: failed program was:
|       program main
| #ifndef __GNUC__
|        choke me
| #endif
|
|       end

....
...
..
.

 
_________________________________________________________________
Put your friends on the big screen with Windows Vista® + Windows Live™.
http://www.microsoft.com/windows/shop/specialoffers.mspx?ocid=TXT_TAGLM_CPC_MediaCtr_bigscreen_102007


More information about the Pw_forum mailing list