I'm trying to build an RPM of 1.3.3 from the SRPM. Despite typical RPM
practice, I need to build ompi so that it installs to a different directory
from /usr or /opt, i.e. what I would get if I just built from source myself
with a --prefix argument to configure.
When I invoke buildrpm with the
rpmbuild likes to pass many of its own options to configure, including
many that set bindir, libdir, etc. explicitly. Try setting _prefix
instead of passing the prefix as a configure_options. For example:
rpmbuild --rebuild --define '_prefix /tmp/bogus'
openmpi-1.3.3-1.src.rpm
On Oc
Hi Bill,
you might want to have a look here if you need a working example of
that:
https://savannah.fzk.de/cgi-bin/viewcvs.cgi/trunk/?root=openmpi-build
We used to generate both SRPMs and RPMs for Open MPI in a previous
project and did in fact specify a separate installation directory :
(%define
On Wed, Sep 30, 2009 at 3:16 PM, Peter Kjellstrom wrote:
> Not MPI aware, but, you could watch network traffic with a tool such as
> collectl in real-time.
collectl is a great idea. I am going to try that now.
--
Rahul
Jonathan Dursi wrote:
We have here installed a couple of installations of OpenMPI 1.3.2, and
we are having real problems with single-node jobs randomly hanging
when using the shared memory BTL, particularly (but perhaps not only)
when using the version compiled with gcc 4.4.0.
The very trivi
On Wed, Sep 30, 2009 at 1:34 AM, Anthony Chan wrote:
> ./configure CC=icc F77=ifort
> MPI_CC=/usr/local/ompi-ifort/bin/mpicc
> MPI_F77=/usr/local/ompi-ifort/bin/mpif77
> --prefix=..
>
> Let me know how it goes.
>
> A.Chan
Thanks! Your command like worked perfect! :)
--
Rahul
