Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] Can I build development RPM from openmpi-1.2.8-1.src.rpm?
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2008-11-11 12:53:28


On Nov 11, 2008, at 11:40 AM, Oleg V. Zhylin wrote:

> mpif90 -g -pg -CB -traceback --static -fno-range-check -L/usr/lib64/
> openmpi/1.2.4-gcc -c forests.f90
> gfortran: unrecognized option '-CB'
> gfortran: unrecognized option '-traceback'
> mpif90 -g -pg -CB -traceback --static -fno-range-check -L/usr/lib64/
> openmpi/1.2.4-gcc -o parf main.f90 parallel.o trees.o bitvectors.o
> instancesets.o options.o utilities.o bootstraps.o forests.o
> importances.o prototypes.o graphics.o support.o
> gfortran: unrecognized option '-CB'
> gfortran: unrecognized option '-traceback'
> /usr/bin/ld: cannot find -lmpi_f90
> collect2: ld returned 1 exit status
> make: *** [parf] Error 1
>
> /usr/bin/ld doesn't see libmpi_f90 despite
>
> ls /usr/lib64/openmpi/1.2.4-gcc/libmpi_f90*
> /usr/lib64/openmpi/1.2.4-gcc/libmpi_f90.la
> /usr/lib64/openmpi/1.2.4-gcc/libmpi_f90.so
> /usr/lib64/openmpi/1.2.4-gcc/libmpi_f90.so.0
> /usr/lib64/openmpi/1.2.4-gcc/libmpi_f90.so.0.0.0

It doesn't see libmpi_f90.so because you specifically asked for the
static library via the --static command line flag (i.e., it's
specifically looking for libmpi_f90.a).

Additionally, you might want to look into -CB and -traceback are
supposed to be doing. gfortran clearly doesn't know what they are --
it's issuing warnings about these parameters.

>
>
> Here is information about MPI setup
>
> mpif90 --showme
> gfortran -I/usr/include/openmpi/1.2.4-gcc/64 -I/usr/include/openmpi/
> 1.2.4-gcc -m64 -pthread -I/usr/lib64/openmpi/1.2.4-gcc -L/usr/lib64/
> openmpi/1.2.4-gcc -lmpi_f90 -lmpi_f77 -lmpi -lopen-rte -lopen-pal -
> ldl -Wl,--export-dynamic -lnsl -lutil -lm -ldl
>
> ompi_info --all >ompi_info.txt
>
> ompi_info.zip is attached to this message
>
> echo $PATH
> /usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib64/ccache:/usr/bin:/bin
>
> echo $LD_LIBRARY_PATH
>
> # contains nothing

Thanks! This all looks normal. I think the root of your issue is
that you are specifically asking for static libraries where there are
none. I don't know if those yum packages provide static libraries or
not; you'll need to ask their maintainer(s). If not, you can compile
RPMs with static libraries via the instructions I sent before, but be
sure to read the FAQ items about creating static libraries -- there
are some pitfalls and complications to deal with, especially if you
are using high-speed interconnects.

-- 
Jeff Squyres
Cisco Systems