Yes, you're right, '/usr/libs' was just a typo. Below is the detailed reproduction on Fedora Core 9 x86_64.
yum install openmpi* This installs 3 rpms from yum repository openmpi x86_64 1.2.4-2.fc9 fedora 127 k openmpi-devel x86_64 1.2.4-2.fc9 fedora 281 k openmpi-libs x86_64 1.2.4-2.fc9 fedora 1.0 M next, I'm trying to compile PARF (http://www.irb.hr/en/cir/projects/info/parf/) and get the following output mpif90 -g -pg -CB -traceback --static -fno-range-check -L/usr/lib64/openmpi/1.2.4-gcc -c -o parallel.o parallel/mpi.f90 gfortran: unrecognized option '-CB' gfortran: unrecognized option '-traceback' cc -Wall -g -pg --static -c support.c [skip] 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 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 WBR Oleg V. Zhylin o...@yahoo.com --- On Tue, 11/11/08, Jeff Squyres <jsquy...@cisco.com> wrote: > From: Jeff Squyres <jsquy...@cisco.com> > Subject: Re: [OMPI users] Can I build development RPM from > openmpi-1.2.8-1.src.rpm? > To: "Open MPI Users" <us...@open-mpi.org> > Date: Tuesday, November 11, 2008, 4:53 PM > On Nov 10, 2008, at 8:21 PM, Oleg V. Zhylin wrote: > > >> Are you saying that you have libmpi_f90.so > available and > >> when you try to run, you get missing symbol > errors? Or are > >> you failing to compile/link at all? > > > > Linking stage fails. When I use mpif90 to produce > actual executable ld reports error that it can't find > -lmpi_f90. The libmpi_f90.so is in /usr/libs but, > > /usr/libs is not a standard linker directory. If > libmpi_f90.so is there, it's probably fairly predictable > that the linker is not finding it. Did you really mean > /usr/lib? > > > again, as I've discovered ld doesn't even try > to look for it. Maybe this is ld problem, or ld in > conjunction with gfortran... > > Can you supply all the information listed here: > > http://www.open-mpi.org/community/help/ > > Additionally, what's the output when you run > "mpif90 --showme"? > > --Jeff Squyres > Cisco Systems > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users ***************************************************************************** ** ** ** WARNING: This email contains an attachment of a very suspicious type. ** ** You are urged NOT to open this attachment unless you are absolutely ** ** sure it is legitimate. Opening this attachment may cause irreparable ** ** damage to your computer and your files. If you have any questions ** ** about the validity of this message, PLEASE SEEK HELP BEFORE OPENING IT. ** ** ** ** This warning was added by the IU Computer Science Dept. mail scanner. ** *****************************************************************************
<<attachment: ompi_info.zip>>
