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 prefers
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!
From: users-bounces_at_[hidden] [mailto:users-bounces_at_[hidden]] On
Behalf Of Mark Kosmowski
Sent: Tuesday, February 12, 2008 5:10 PM
Subject: Re: [OMPI users] openMPI on 64 bit SUSE 10.2 OS
Are you pointing to the 64-bit build of HYPRE? For that matter, like
Jeff asked, are you sure that each library path that you are defining
goes to a 64-bit library path?
Mark E. Kosmowski
checking for Fortran 77 libraries of mpif90...
checking for Fortran libraries of mpif90...
ib -L/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../.. -lHYPRE
checking for dseupd_ in -larpack... yes
checking for pdneupd_ in -lparpack... no
configure: WARNING: No parallel arpack found.
checking for HYPRE_IJMatrixCreate in -lHYPRE... no
configure: WARNING: HYPRE not found, some functionaly will be
checking for umf4def_ in -lumfpack... yes
checking for mtc_init in -lmatc... yes
checking for main in -lm... yes
configure: error: The MPI version needs parpack. Disabling MPI.
Pei-Ying Hsieh, Ph.D.
Staff Product Engineer
Siemens Healthcare Diagnostics Inc.
511 Benedict Ave., MS 32
Tarrytown, NY 10591
What puzzles me is that, on 32 bit OpenSUSE, I was able to
solver without any issue using the same script. I am planning
HYPRE library, but, configure file indicated that it cannot find
either which is another puzzle to me. I will look into this
Is it possible that this could be a problem with /usr/lib64 as
Just a thought...
Jeff F. Pummill
Senior Linux Cluster Administrator
University of Arkansas
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]