The ABINIT Users Mailing List ( CLOSED )

[<osirixu-abinit@yahoo.com.cn>]

Dear Pierre and abinit users,

    Thank you for your reply. Well, the problem is
even when I set the following flags in the command
line after configure:

./configure --build=pentium3-intel-linux-gnu \
 build_blas=no \
 build_lapack=no \
 FCFLAGS_OPT="-r8 -w95 -O2 -pc64 -tpp6 -unroll -cm
-tune pn3 -arch pn3 -xK -ipo -vec-report0" \
 CFLAGS_OPT="-O2 -mcpu=pentiumpro -msse -xK
-vec-report0" \
 CXXFLAGS_OPT="-O2 -mcpu=pentiumpro -msse -xK
-vec-report0" \
 --with-fortran-ldflags=-i-static \
 --with-blas-prefix=/usr/local/lib/mkl \
 --with-lapack-prefix=/usr/local/lib/mkl

abinit still cann't identify my MKL library, and try
to build the BLAS and LAPACK libraries interally. The
other problems I mentioned in the earlier post still
exist.

    Did any guy use the Intel MKL library to build
abinit? 

    greetings,
      Rex
    June 1, 2006


--- Anglade Pierre-Matthieu <anglade@gmail.com> wrote:

> Hi,
> 
> One of the simplest way to get precisely the desired
> FC and FCFLAGS is to
> set them on the command line:
> eg: ../configure FC=/usr/opt/.../ifc FCFLAGS="-O5
> -allkindofoptyou'dlike"
> This is what I usualy do.
> 
> regards
> PMA
> 

> On 5/30/06, osirixu-abinit@yahoo.com.cn
> <osirixu-abinit@yahoo.com.cn> wrote:
> >
> > Dear abinitors,
> >
> >     I wish to build abinit with intel fortran
> compiler
> > (ifc 9.0), intel C compiler (icc 9.0), and intel
> mkl
> > library (mkl 8.0), on an AMD Athlon (=pentium3)
> x86
> > linux platform. I do have explicitly set the
> variables
> > of LD_LIBRARY_PATH and INTEL_LICENSE_FILE in bash.
> >
> >
> >
>
LD_LIBRARY_PATH="/opt/intel/mkl/8.0.1/lib/32:/opt/intel/cc/9.0/lib:/opt/intel/fc/9.0/lib:/usr/local/lib"
> > And I have set the following variables in the
> > <hostname>.ac file:
> >        CC="icc"
> >        CXX="icpc"
> >        FC="ifort"
> > the configure script mis-recognised my cpu as
> > pentium4, and mis-recognised the icc and icpc as
> GNU
> > compilers, and it also can't find the mkl library
> too.
> > (The output of configure script is appended
> below.)
> >
> >     Though after I announced the following
> variables
> > in the <hostname>.ac file, the configure script
> can
> > recognise both of the icc and icpc compiler's
> version.
> > (The difference of the output of configure script
> with
> > the former one is also appended below.)
> >      abi_cpu_model=pentium3
> >      cc_type=intel
> >      cc_version=9.0
> >      cxx_type=intel
> >      cxx_version=9.0
> >      fc_type=intel
> >      fc_version=9.0
> >      with_lapack_prefix="/usr/local/lib/mkl"
> >      with_blas_prefix="/usr/local/lib/mkl"
> > where the last two lines is set because abinit
> look
> > for the LAPACK and blas library in "<prefix>/lib",
> i
> > just linked the correspding directory of mkl
> library
> > to "/usr/local/lib/mkl/lib" directory. Still the
> > configure script cann't find the mkl library, but
> > following files do be there:
> > /usr/local/lib/mkl/lib/libguide.a
> > /usr/local/lib/mkl/lib/libmkl_lapack.a
> > /usr/local/lib/mkl/lib/libmkl_ia32.a
> > /usr/local/lib/mkl/lib/libpthread.a
> >
> >     Well, though it seems can recognise the cpu
> model
> > after the modification, and set the following
> flags in
> > Makefile automatically:
> > FCFLAGS =   -extend_source -vec-report0
> > FCFLAGS_BLAS =
> > FCFLAGS_LAPACK =
> > FCFLAGS_OPT = -O3 -arch pn3 -tune pn3 -tpp6 -xK
> > then in the process of compilation, I cann't see
> any
> > no optimization flags in the output during the
> > compiling process, and it seems build the lapack
> and
> > blas libraries internally. Though finally I can
> > successfully get the abinit, the code cann't run
> as
> > efficiently as it could.
> > I don't know how to fix this problem? Any advice
> or
> > suggestions will be appreciated!
> >
> >     Besides, in my personal view, if we can
> optionally
> > self-set the varibles for compilers, the flags,
> and
> > the math libraries, in a single makefile just like
> > some other ab initio code, then we could build
> abinit
> > compatible with more different compilers, and math
> > libraries. Because there are so many platforms, so
> > many compilers, and so many versions of a
> compiler, it
> > would be an expensive job to maintain the
> configure
> > script to the version updates of cpus, compilers,
> and
> > math libraries. Alternatively, a list of
> optimization
> > flags, and the math-libraries we have to use, on a
> > README file may be more flexible and applicable to
> > users.
> >
> >      Best Wishes!
> >
> >       Rex
> >      May 30, 2006
> >
> >
> > # ./configure >config1.log
> > ######################> the content of config1.log
> > <###########################
> >
> >
> >
>
==============================================================================
> > === Build environment
> >                      ===
> >
> >
> >
>
==============================================================================
> > checking build system type... i686-pc-linux-gnu
> > checking host system type... i686-pc-linux-gnu
> > checking target system type... i686-pc-linux-gnu
> > checking for a BSD-compatible install...
> > /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking for gawk... gawk
> > checking whether make sets $(MAKE)... yes
> > configure: reading options from ./localhost.ac
> >
> >
> >
>
==============================================================================
> > === Utilities
> >                      ===
> >
> >
> >
>
==============================================================================
> > checking whether make sets $(MAKE)... (cached) yes
> > checking for a BSD-compatible install...
> > /usr/bin/install -c
> > checking whether ln -s works... yes
> > checking for sh... /bin/sh
> > checking for perl... /usr/bin/perl
> > checking for python... /usr/bin/python
> > checking for rm... /bin/rm
> > checking for mv... /bin/mv
> > checking for tar... /bin/tar
> > checking for markdown... /usr/bin/markdown
> > checking for latex... /usr/bin/latex
> > checking for dvips... /usr/bin/dvips
> > checking for dvipdf... /usr/bin/dvipdf
> > checking for ps2pdf... /usr/bin/ps2pdf
> > configure: Using internal version of MarkDown
> >
> >
> >
>
==============================================================================
> > === Libraries and linking
> >                      ===
> >
> >
> >
>
==============================================================================
> > checking for ar... /usr/bin/ar
> > checking for ranlib... ranlib
> > checking for a sed that does not truncate
> output...
> > /bin/sed
> > checking for style of include used by make... GNU
> > checking for gcc... icc
> > checking for C compiler default output file
> name...
> > a.out
> > checking whether the C compiler works... yes
> > checking whether we are cross compiling... no
> > checking for suffix of executables...
> > checking for suffix of object files... o
> > checking whether we are using the GNU C
> compiler...
> > yes
> > checking whether icc accepts -g... yes
> > checking for icc option to accept ANSI C... none
> 
=== message truncated ===



                
___________________________________________________________ 
抢注雅虎免费邮箱-3.5G容量，20M附件！ 
http://cn.mail.yahoo.com