At 11:19 PM 9/26/2004, Raphael Lullis wrote:
>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.
The normal way is to build a copy of lam which uses ifort as fc. The ifort
environment variables must be set when building lam, and linking the
application. If either lam or the application has dynamic link, the ifort
LD_LIBRARY_PATH must be set at run time as well.
In all cases, the real linker is gnu ld. Using ifort to drive ld will pass
the necessary ifort libraries to ld. Using mpif77 built with ifort will
pass the lam libraries as well. If you are only re-linking your
application, it may be possible to do so without the ifort built copy of
lam, but you will need to add the -L and -l designations which lam requires
to your ifort command.
Tim Prince
|
