Thank all of you!
is that
export LD_LIBRARY_PATH=/path/to/lam/lib:$LD_LIBRARY_PATH ??
the MPICH has been installed in our cluster before, so I modified the $PATH,
just removed the MPICH bin and added the LAM bin, then when type "mpicc" in
command line, it will be in the Lam/bin, not mpich/bin
however, if anyone else want to use MPICH, he/she has to modified the $PATH,
too.
any solution else?
2006/3/3, Andrew Friedley <afriedle_at_[hidden]>:
>
> Mars Lenjoy wrote:
> > hello,
> > i want to run lamtest, how to configure lamtest to lammpi, not mpich.
> > how to add the parameters after ./configure
> > or any envirenment var?
>
> As others have indicated, you need to prefix your PATH and
> LD_LIBRARY_PATH environment variables with the path to your LAM
> installation.
>
> If you're using bash, you would do something like this:
>
> export PATH=/path/to/lam/bin:$PATH
> export LD_LIBRARY_PATH=/path/to/lam/lib:$PATH
>
> Note the /bin and /lib at the end of the new directory paths. Once you
> have this set, you can double check by running 'laminfo'. You might
> also look at the version and build date to make sure you are running the
> right LAM version.
>
> No arguments to configure should be needed for lamtests if the
> environment variables are in place.
>
> Andrew
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
