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
b64/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
>
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
om>
> Subject: Re: [OMPI users] Can I build development RPM from
> openmpi-1.2.8-1.src.rpm?
> To: o...@yahoo.com
> Cc: "Open MPI Users" <us...@open-mpi.org>
> Date: Monday, November 10, 2008, 9:26 PM
> On Nov 10, 2008, at 2:18 PM, Oleg V. Zhylin wrote:
>
On Nov 10, 2008, at 2:18 PM, Oleg V. Zhylin wrote:
Right -- OMPI builds shared libraries by default.
What is the proper way to build static libraries from RPM? Or
tarball is the only option to accomplish this?
You can pass any options to OMPI's configure script through the
rpmbuild
ience building MPI on Fedora? Are there any additional
steps required other then yum install openmpi*?
WBR Oleg V. Zhylin o...@yahoo.com
--- On Mon, 11/10/08, Jeff Squyres <jsquy...@cisco.com> wrote:
> From: Jeff Squyres <jsquy...@cisco.com>
> Subject: Re: [OMPI users] Can I
Hi,
I would like to to build OpenMPI from openmpi-1.2.8-1.src.rpm. I've tried
plain rpmbuild and rpmbuild ... --define 'build_all_in_one_rpm 1' but
resulting rpm doesn't conain any *.a libraries.
I think this is a problem because I've straced mpif90 and discovered that ld
invoked from
