This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
Is it possible that this could be a problem with /usr/lib64 as opposed
Just a thought...
Jeff F. Pummill
Senior Linux Cluster Administrator
University of Arkansas
Hsieh, Pei-Ying (MED US) wrote:
> Hi, Edgar and Galen,
> Thanks for the quick reply!
> What puzzles me is that, on 32 bit OpenSUSE, I was able to compile elmer
> solver without any issue using the same script. I am planning to use
> HYPRE library, but, configure file indicated that it cannot find hypre
> either which is another puzzle to me. I will look into this further.
> -----Original Message-----
> From: users-bounces_at_[hidden] [mailto:users-bounces_at_[hidden]] On
> Behalf Of Edgar Gabriel
> Sent: Tuesday, February 12, 2008 4:28 PM
> To: Open MPI Users
> Subject: Re: [OMPI users] openMPI on 64 bit SUSE 10.2 OS
> I doubt that this has to do anything with the platform. We are running
> here Open MPI on a 64bit architecture using SuSe 10.2 since quite a
> while successfully. However, you configure log is indicating, the
> parpack could not be found, so you might have to change the CFLAGS and
> LDFLAGS in order for you configure script to find the according library.
> Hsieh, Pei-Ying (MED US) wrote:
>> configure: error: The MPI version needs parpack. Disabling MPI.
> 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]
> Thank you
> users mailing list