Thanks for the email.
Yes, I did define CC/CXX/FC/F77/LDFLAGS.. Before configure. All set to
From: users-bounces_at_[hidden] [mailto:users-bounces_at_[hidden]] On
Behalf Of James A. Peltier
Sent: Wednesday, February 13, 2008 11:33 AM
To: Open MPI Users
Subject: Re: [OMPI users] openMPI on 64 bit SUSE 10.2 OS
Hsieh, Pei-Ying (MED US) wrote:
> Hi, Mark,
> When I installed HYPRE, I simply did "./configure
> --prefix=/usr/local/hypre2.0", then make, make install. All libraries
> seems to be static libraries.
> As for openmpi, I did "./configure --prefix=/usr/local/openmpi
> --enable-static --disable-shared", then, make all install (elmer
> statically linked). So, all openmpi static library should resides in
> /usr/local/openmpi. A simple hello_mpi.c (.f90) ran fine.
> During elmer configuration, one of the steps is to build blas/parpack
> libraries. Which was successful (I got libparpack.a under
> ELMER_HOME/lib). It is not clear to me why at the final step of elmer
> configuration, it complains about not finding HYPRE and parpack.
> I also suspect about the /usr/lib64 business. Trying to sort out
> whether this is an openMPI issue (on 64 bit SuSE) or elmer issue.
> Thanks a lot!
Did you ensure that all of the applications were built using the OpenMPI
compilers? Sometimes you *have* to define the CC, CXX, etc when
James A. Peltier
Technical Director, RHCE
SCIRF | GrUVi @ Simon Fraser University - Burnaby Campus
Phone : 778-782-3610
Fax : 778-782-3045
Mobile : 778-840-6434
E-Mail : jpeltier_at_[hidden]
Website : http://gruvi.cs.sfu.ca | http://scirf.cs.sfu.ca
MSN : subatomic_spam_at_[hidden]
users mailing list
This message and any included attachments are from Siemens Medical Solutions
and are intended only for the addressee(s).
The information contained herein may include trade secrets or privileged or
otherwise confidential information. Unauthorized review, forwarding, printing,
copying, distributing, or using such information is strictly prohibited and may
be unlawful. If you received this message in error, or have reason to believe
you are not authorized to receive it, please promptly delete this message and
notify the sender by e-mail with a copy to Central.SecurityOffice_at_[hidden]