The LAPACK forum has moved to https://github.com/Reference-LAPACK/lapack/discussions.

Detecting Fortran/C compiler

Open discussion regarding features, bugs, issues, vendors, etc.

Detecting Fortran/C compiler

Postby yamen » Wed Mar 26, 2008 6:34 am

I am trying to install Scalapack through the installer 0.9.
I am facing this error since the morning : Detecting fortran compiler ..... unkown
Detecting C compiler ..... unkown
I said error because i am suspiscious that it is the origin of the errors when trying to use blas library. problem of linking
yamen
 
Posts: 10
Joined: Tue Mar 25, 2008 11:11 am

Re: Detecting Fortran/C compiler

Postby buttari » Wed Mar 26, 2008 1:20 pm

yamen wrote:I am trying to install Scalapack through the installer 0.9.
I am facing this error since the morning : Detecting fortran compiler ..... unkown
Detecting C compiler ..... unkown
I said error because i am suspiscious that it is the origin of the errors when trying to use blas library. problem of linking


Yamen,
what compilers do you have? and what errors do you get when linking to BLAS? you should make sure, btw, that the compiler you provide to the installer is the same that you used for compiling the BLAS (if you compiled it).
Let us have more info in order to support your request.
Thanks

alfredo
buttari
 
Posts: 51
Joined: Tue Jul 11, 2006 2:11 pm

Postby yamen » Thu Mar 27, 2008 5:59 am

Thanks I have resolved this problem in fact my F77 compiler is g77 et my C compiler is gcc. So I disabled the test in the script of framework.py and set it manually to GNU.

But the problem now that I am facing a problem in the communication betwwen fortran and C when testing the libraries generated there is an error continuously "undefined reference to" and the name of functions. I think that there is a problem with underscoring done by fortran. how i can beat this? is it a matter of flags ? plz give me some hints
yamen
 
Posts: 10
Joined: Tue Mar 25, 2008 11:11 am

Postby buttari » Thu Mar 27, 2008 6:41 am

yamen wrote:Thanks I have resolved this problem in fact my F77 compiler is g77 et my C compiler is gcc. So I disabled the test in the script of framework.py and set it manually to GNU.

But the problem now that I am facing a problem in the communication betwwen fortran and C when testing the libraries generated there is an error continuously "undefined reference to" and the name of functions. I think that there is a problem with underscoring done by fortran. how i can beat this? is it a matter of flags ? plz give me some hints


Obvious...
the framework.py script is there for a good reason and should not be disabled...
The F77 and C compilers should be set to mpif77 and mpicc respectively. If you have them in your PATH the installer can detect them automatically, otherwise you can provide them through the --mpicc=[CMD] and --mpif77=[CMD] flags.
buttari
 
Posts: 51
Joined: Tue Jul 11, 2006 2:11 pm

Postby yamen » Thu Mar 27, 2008 11:55 am

buttari wrote:
yamen wrote:Thanks I have resolved this problem in fact my F77 compiler is g77 et my C compiler is gcc. So I disabled the test in the script of framework.py and set it manually to GNU.

But the problem now that I am facing a problem in the communication betwwen fortran and C when testing the libraries generated there is an error continuously "undefined reference to" and the name of functions. I think that there is a problem with underscoring done by fortran. how i can beat this? is it a matter of flags ? plz give me some hints


Obvious...
the framework.py script is there for the framework.py script is there for a ga good reason and should not be disabled...
The F77 and C compilers should be set to mpif77 and mpicc respectively. If you have them in your PATH the installer can detect them automatically, otherwise you can provide them through the --mpicc=[CMD] and --mpif77=[CMD] flags.


Yes I konow that the framework.py if there for a good reason... which is testing and identifying your compilers and since the test wasnt efficient I dont know why ( result unkown) then I write it manually
yamen
 
Posts: 10
Joined: Tue Mar 25, 2008 11:11 am

Postby buttari » Thu Mar 27, 2008 4:32 pm

yamen wrote:
buttari wrote:
yamen wrote:Thanks I have resolved this problem in fact my F77 compiler is g77 et my C compiler is gcc. So I disabled the test in the script of framework.py and set it manually to GNU.

But the problem now that I am facing a problem in the communication betwwen fortran and C when testing the libraries generated there is an error continuously "undefined reference to" and the name of functions. I think that there is a problem with underscoring done by fortran. how i can beat this? is it a matter of flags ? plz give me some hints


Obvious...
the framework.py script is there for the framework.py script is there for a ga good reason and should not be disabled...
The F77 and C compilers should be set to mpif77 and mpicc respectively. If you have them in your PATH the installer can detect them automatically, otherwise you can provide them through the --mpicc=[CMD] and --mpif77=[CMD] flags.


Yes I konow that the framework.py if there for a good reason... which is testing and identifying your compilers and since the test wasnt efficient I dont know why ( result unkown) then I write it manually


Yamen,
the script also does other things.
As for the compiler, the script tries to detect which compiler you are using in order to set a few parameters that are essential for some compilers (e.g., the intel compilers). In the case where it says "unkown" it doesn't mean that it's not going to work.
However, if you want us to help you, please do what I asked you to do (either put mpicc and mpif77 in your PATH or provide them through the --mpicc and --mpif77 flags). Then, if you still have an error, please let us now what the error is (you should copy/paste it here). Otherwise, I can't do more than this.

Alfredo
buttari
 
Posts: 51
Joined: Tue Jul 11, 2006 2:11 pm

Postby yamen » Fri Mar 28, 2008 4:12 am

thank you for your help but the mpicc and mpif77 exist in PATH and so i think the problem is another.
In fact I can use as fortran compiler f77 or ifort.
I tried with f77 but it adds underscore to the functions and so when testing routines of scalapack manu errors of undefined reference.
So I tried with ifort ( intel compiler ) since it doesnt add underscore but finally i got these errors ;

geo2127% setup.py --mpibindir=/nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/bin --mpicc=mpicc --mpif77="mpif77 -lg2c /nfs/netapp1/IRP_home/ndelader/programation/mpi/hello_world/test_init.o /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libcprts.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libsvml.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libifport.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libifcoremt.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libimf.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libguide.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libirc.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libirc_s.a" --mpiincdir=/nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/include --ccflags=-DAdd_ --fcflags= --makecmd=make --downlapack --downblas --downblacs
========================================
Setting up the framework

MPI bin dir is /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/bin
mpicc is mpicc
mpif77 is mpif77 -lg2c /nfs/netapp1/IRP_home/ndelader/programation/mpi/hello_world/test_init.o /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libcprts.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libsvml.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libifport.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libifcoremt.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libimf.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libguide.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libirc.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libirc_s.a
MPI include dir is /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/include
C flags are -DAdd_
Fortran flags are
Checking if mpicc works... yes
Checking if mpif77 works... yes
Setting Fortran mangling...
Setting download command... urllib2
Setting ranlib command... /usr/bin/ranlib
Detecting Fortran compiler... Intel
Detecting C compiler... GNU
Selected C compiler flags: -DAdd_
Selected Fortran77 compiler flags:
Selected loader flags:
Selected NOOPT flags: -mp
Checking loader... works

========================================
BLAS installation/verification
========================================

Downloading and installing BLAS...
The reference BLAS library is being installed.
Don't expect high performance from this reference library!
If you want performance, you need to use an optimized BLAS library and,
to avoid unnecessary complications, if you need to compile this optimized BLAS
library, use the same compiler you're using here.
... done. (log is in log/blacslog)
done.

========================================
Lapack installation/verification
========================================
Setting ETIME... EXT_ETIME
Writing make.inc... done.
Compiling LAPACK (this will take several minutes)... done. (log is in log/laplog)
done.

========================================
BLACS installation/verification
========================================
Setting TRANSCOMM... -DCSameF77

Writing Bmake.inc... done.
Compiling BLACS... done. (log is in log/blacslog)

========================================
ScaLAPACK installer is starting now. Buckle up!
========================================
Writing SLmake.inc... done.
Compiling ScaLAPACK... done. (log is in log/scalog)
Compiling test routines...


ScaLAPACK: error building ScaLAPACK test routines
stderr:
****************************************
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/libscalapack.a(pslacon.o)(.text+0x458): In function `pslacon_':
: undefined reference to `f_lanint_val'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/libscalapack.a(pslacon.o)(.text+0x655): In function `pslacon_':
: undefined reference to `f_lanint_val'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/libscalapack.a(pslacon.o)(.text+0x920): In function `pslacon_':
: undefined reference to `f_lanint_val'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/libscalapack.a(pslacon.o)(.text+0xb37): In function `pslacon_':
: undefined reference to `f_lanint_val'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/libscalapack.a(pslacon.o)(.text+0xd41): In function `pslacon_':
: undefined reference to `f_lanint_val'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/lib/libreflapack.a(slamch.o)(.text+0x22a): In function `slamch_':
: undefined reference to `__powr4i4'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/lib/libreflapack.a(slamch.o)(.text+0x261): In function `slamch_':
: undefined reference to `__powr4i4'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/lib/libreflapack.a(slamch.o)(.text+0x380): In function `slamc2_':
: undefined reference to `__powr4i4'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/lib/libreflapack.a(slamch.o)(.text+0x4ee): In function `slamc2_':
: undefined reference to `__powr4i4'
collect2: ld returned 1 exit status
make[1]: *** [/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/TESTING/xslu] Error 1
make: *** [scalapackexe] Error 2
yamen
 
Posts: 10
Joined: Tue Mar 25, 2008 11:11 am

Postby buttari » Fri Mar 28, 2008 4:54 am

yamen wrote:thank you for your help but the mpicc and mpif77 exist in PATH and so i think the problem is another.
In fact I can use as fortran compiler f77 or ifort.
I tried with f77 but it adds underscore to the functions and so when testing routines of scalapack manu errors of undefined reference.
So I tried with ifort ( intel compiler ) since it doesnt add underscore but finally i got these errors ;

geo2127% setup.py --mpibindir=/nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/bin --mpicc=mpicc --mpif77="mpif77 -lg2c /nfs/netapp1/IRP_home/ndelader/programation/mpi/hello_world/test_init.o /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libcprts.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libsvml.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libifport.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libifcoremt.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libimf.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libguide.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libirc.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libirc_s.a" --mpiincdir=/nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/include --ccflags=-DAdd_ --fcflags= --makecmd=make --downlapack --downblas --downblacs
========================================
Setting up the framework

MPI bin dir is /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/bin
mpicc is mpicc
mpif77 is mpif77 -lg2c /nfs/netapp1/IRP_home/ndelader/programation/mpi/hello_world/test_init.o /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libcprts.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libsvml.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libifport.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libifcoremt.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libimf.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libguide.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libirc.a /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/lib/libirc_s.a
MPI include dir is /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/include
C flags are -DAdd_
Fortran flags are
Checking if mpicc works... yes
Checking if mpif77 works... yes
Setting Fortran mangling...
Setting download command... urllib2
Setting ranlib command... /usr/bin/ranlib
Detecting Fortran compiler... Intel
Detecting C compiler... GNU
Selected C compiler flags: -DAdd_
Selected Fortran77 compiler flags:
Selected loader flags:
Selected NOOPT flags: -mp
Checking loader... works

========================================
BLAS installation/verification
========================================

Downloading and installing BLAS...
The reference BLAS library is being installed.
Don't expect high performance from this reference library!
If you want performance, you need to use an optimized BLAS library and,
to avoid unnecessary complications, if you need to compile this optimized BLAS
library, use the same compiler you're using here.
... done. (log is in log/blacslog)
done.

========================================
Lapack installation/verification
========================================
Setting ETIME... EXT_ETIME
Writing make.inc... done.
Compiling LAPACK (this will take several minutes)... done. (log is in log/laplog)
done.

========================================
BLACS installation/verification
========================================
Setting TRANSCOMM... -DCSameF77

Writing Bmake.inc... done.
Compiling BLACS... done. (log is in log/blacslog)

========================================
ScaLAPACK installer is starting now. Buckle up!
========================================
Writing SLmake.inc... done.
Compiling ScaLAPACK... done. (log is in log/scalog)
Compiling test routines...


ScaLAPACK: error building ScaLAPACK test routines
stderr:
****************************************
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
ifort: Command line warning: no action performed for specified file(s)
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/libscalapack.a(pslacon.o)(.text+0x458): In function `pslacon_':
: undefined reference to `f_lanint_val'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/libscalapack.a(pslacon.o)(.text+0x655): In function `pslacon_':
: undefined reference to `f_lanint_val'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/libscalapack.a(pslacon.o)(.text+0x920): In function `pslacon_':
: undefined reference to `f_lanint_val'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/libscalapack.a(pslacon.o)(.text+0xb37): In function `pslacon_':
: undefined reference to `f_lanint_val'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/libscalapack.a(pslacon.o)(.text+0xd41): In function `pslacon_':
: undefined reference to `f_lanint_val'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/lib/libreflapack.a(slamch.o)(.text+0x22a): In function `slamch_':
: undefined reference to `__powr4i4'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/lib/libreflapack.a(slamch.o)(.text+0x261): In function `slamch_':
: undefined reference to `__powr4i4'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/lib/libreflapack.a(slamch.o)(.text+0x380): In function `slamc2_':
: undefined reference to `__powr4i4'
/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/lib/libreflapack.a(slamch.o)(.text+0x4ee): In function `slamc2_':
: undefined reference to `__powr4i4'
collect2: ld returned 1 exit status
make[1]: *** [/nfs/netapp1/IRR_home/ybelhass/projet/ScaLAPACK/ScaLAPACK.1.8/scalapack_installer_0.91/build/scalapack-1.8.0/TESTING/xslu] Error 1
make: *** [scalapackexe] Error 2


Yamen,
why do you want to provide such a complicated mpif77 command? the ifort compiler will automatically link to all thos libraries that you're passing. Your setup command should be as simple as this:

Code: Select all
./setup.py --mpicc=mpicc --mpif77=mpif77 --mpiincdir=/nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/include --downlapack --downblas --downblacs


If this does not work, please let me now what error message you get (again copy/paste of the setup.py log would be great).
Thanks

alfredo
buttari
 
Posts: 51
Joined: Tue Jul 11, 2006 2:11 pm

Postby yamen » Fri Mar 28, 2008 7:48 am

I ve done what u told me

geo2127% setup.py --mpicc=mpicc --mpif77=mpif77 --mpiincdir=/nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/include --downlapack --downblas --downblacs
========================================
Setting up the framework

mpicc is mpicc
mpif77 is mpif77
MPI include dir is /nfs/softs/TOOLS/Intel/compiler-9.1/em64t/mpich/include
Checking if mpicc works... yes
Checking if mpif77 works... yes
Setting Fortran mangling... -Df77IsF2C
Setting download command... urllib2
Setting ranlib command... /usr/bin/ranlib
Detecting Fortran compiler... GNU
Detecting C compiler... GNU
Selected C compiler flags: -O3
Selected Fortran77 compiler flags: -O3
Selected loader flags:
Selected NOOPT flags:
Checking loader... works

========================================
BLAS installation/verification
========================================

Downloading and installing BLAS...
The reference BLAS library is being installed.
Don't expect high performance from this reference library!
If you want performance, you need to use an optimized BLAS library and,
to avoid unnecessary complications, if you need to compile this optimized BLAS
library, use the same compiler you're using here.
... done. (log is in log/blacslog)
done.

========================================
Lapack installation/verification
========================================
Setting ETIME... EXT_ETIME
Writing make.inc... done.
Compiling LAPACK (this will take several minutes)... done. (log is in log/laplog)
done.

========================================
BLACS installation/verification
========================================
Setting TRANSCOMM...

1BLACS: Error in transcomm setting! cannot compile
stderr:
****************************************
tmpf.o(.text+0xc): In function `MAIN__':
: undefined reference to `mpi_init__'
tmpf.o(.text+0x2d): In function `MAIN__':
: undefined reference to `mpi_finalize__'
tmpf.o(.data+0x0): undefined reference to `mpi_dup_fn__'
tmpf.o(.data+0x8): undefined reference to `mpi_null_delete_fn__'
tmpf.o(.data+0x10): undefined reference to `mpi_null_copy_fn__'
collect2: ld returned 1 exit status

yamen
 
Posts: 10
Joined: Tue Mar 25, 2008 11:11 am


Return to User Discussion

Who is online

Users browsing this forum: No registered users and 4 guests