Thanks for the quick response, Tim.
Well, I tried using the regular rpm to run this particular
application, but when I was making my app, it complained that it
needed to use the same linker that the mpi environment was using.
Since my app _must_ use ifort, I compiled everything with it.
I just set LD_LIBRARY_PATH and put it in .bashrc. Everything is
working now. Now I need to configure the mpi environment.
On Sun, 26 Sep 2004 21:32:29 -0700, Tim Prince <tprince_at_[hidden]> wrote:
> At 07:29 PM 9/26/2004, Raphael Lullis wrote:
>
> >I'm trying to install lam 7.1 on a slackware 10.0 pc, so that I can
> >test some programs that require the MPI and Intel Fortran compiler.
> >
> >I've run into a little trouble to get ifort running, but now I'm able
> >to run the compiler, apparently without trouble.
> >
> >Thing is, I followed the instructions to install lam 7.1, and I got no
> >errors during configure, make and make install. I did, however, get
> >error messages when trying to execute laminfo or any other
> >lam-program.
> >
> >Apparently, the error is related to a missing library, libcptrs.so.5.
> >
> >Assuming my compilers are working correctly, what else do I need to
> >setup to get lam running? I did set the compiler variables and
> >"./configure" showed it would use the intel compilers. I did *not* set
> >any ld_library_path variable. I think there lies my mistake.... Is
> >this so? what else do I need to set up, or that is not the thing that
> >I need to work on?
>
> Yes, LD_LIBRARY_PATH would need to include the path at run time to the
> Intel compiler library, including libcprts, same as when you run the
> compiler, unless you linked -static. Normally, we would not build a lam
> requiring this library, as the default for Intel icc 8.x is to use
> libstdc++ (if present at installation on a .rpm supporting distro) rather
> than libcprts. We use g++ rather than icc anyway, unless we know we have
> C/C++ code which depends on icc for performance. If you link with Intel
> Fortran, non-static, you will need that library path, but normally not for
> STL support. There is no problem using g++ (in the normal ranges) together
> with Intel Fortran.
> If you start a dynamic linked lam without LD_LIBRARY_PATH set correctly,
> you may have to lamhalt or kill lamd, set the correct PATH, and
> lamboot. When running on the x86-64 OS, you must have the consistent
> version of PATH and LD_LIBRARY_PATH, as there is nothing automatic to take
> care of getting the proper version (32- vs 64-bit) of either lam or the
> libraries. Sorry if "slackware 10 pc" carries more information than it
> appears.
>
>
> Tim Prince
>
>
|
