At 11:25 PM 11/1/2004, wdz03_at_[hidden], wrote:
> >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?
..a libraries in /usr/bin64 would be used only if you link your application
in 64-bit mode with static options, or there are no corresponding shared
libraries present. Chances are that you didn't install a 32-bit copy of
lam, which would be required if you want to run a 32-bit
application. Renaming libraries will not change them from static to
dynamic, or from 64- to 32-bit mode. If you are trying to run a 32-bit
dynamic linked application, I expect you will have to build a corresponding
copy of lam, and you will have to pay attention to keeping straight on 32-
vs 64-bit installations, including setting your PATH and LD_LIBRARY_PATH so
that the 32-bit version comes first. I have never seen an installation
which does this automatically.
Tim Prince
|
