>From: Jeff Squyres <jsquyres_at_[hidden]>
>Reply-To: General LAM/MPI mailing list <lam_at_[hidden]>
>To: General LAM/MPI mailing list <lam_at_[hidden]>
>Subject: Re: LAM: Where is the file: liblamf77.mpi.so.0
>
>On Oct 31, 2004, at 8:52 PM, "" <wdz03_at_[hidden]> wrote:
>
> > I have run the lam-mpi successfully. But when I run a program based
> > on the lam, an error occured: liblamf77.mpi.so.0 not found.
>
> I'm not quite sure what you mean here -- you said that you're able to
> run LAM but then not able to run LAM... Do you mean that you are able
> to run LAM commands with no problem, but then cannot run MPI
> applications that were compiled with LAM?
>
> > Then I find many .so.0 files are missing.
>
> Besides liblamf77mpi.so, what else is missing?
You are right. I installed the lam from the FC2-linux lam RPM, whose version is
7.03. I can run LAM successfully, but I can not run the lam applications for
lacking of some .so files.
This morning I re-installed the FC2-linux to a full installation, but still
these three files are missing:
liblamf77mpi.so.0
libmpi.so.0
liblam.so.0
I found the following name-similar three files in /usr/bin64
liblamf77mpi.a
libmpi.a
liblam.a
I tried to rename the .a files to .so.0 files, but it doesn't work.
What are the differences between the .so.0 files and .a files?
Have you any suggestions?
Thank you!
>
> liblamf77mpi.so is part of LAM, but LAM is distributed by most Linux
> distributions. So it depends on how you installed LAM -- there are
> typically 2 options: 1) compiling from a source tarball from the LAM
> web site, 2) installing an RPM (or set of RPMs) for your Linux distro.
>
> If you compiled LAM yourself from a source tarball, then all the
> libraries (including liblamf77mpi.so) should be under $prefix/lib. If
> you didn't specify --prefix, it defaults to /usr/local. Your
> description is not verbose enough to tell if the following is a
> problem, but if you chose a non-standard prefix (and possibly even
> /usr/local -- depending on how your Linux distro is setup), you may
> need to ensure that LD_LIBRARY_PATH includes $prefix/lib (e.g.,
> /usr/local/lib) so that the run-time linker can find the LAM shared
> libraries.
>
> If you're installing a Linux distro's RPM of LAM/MPI, then I can't say
> where that library is -- it's up to whoever made that RPM (i.e., each
> Linux distro does it a little differently). Some distros actually
> split the LAM package into multiple RPMs (devel, runtime, etc.); you
> may need to install more than one LAM RPM.
>
> I'm guessing that you're installing from RPM because LAM source
> tarballs build static libraries by default, not shared libraries. You
> may wish to examine the list of files contained in your RPM(s) with the
> "rpm" command. For example:
>
> rpm -qpl lam-7.1.1-1.i586.rpm
>
> --
> {+} Jeff Squyres
> {+} jsquyres_at_[hidden]
> {+} http://www.lam-mpi.org/
>
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
