Hi,
Can you send the lamtests configure output and the corresponding
config.log?
Also make sure that mpi.h is present in /usr/local/lam_mpi/bin and you
have the right permissions on it.
Amey S. Dharurkar
----------------------------------------------------------
Graduate Student, Indiana University
Ph. O:(812)855-3609, H:(812)331-8203
On Sun, 4 Apr 2004, Andy Young wrote:
>
> --- Amey Dharurkar <adharurk_at_[hidden]> wrote:
> >
> > Hi,
> > lamtests configure is unable to find the mpi.h
> > because *mpicc* (and other
> > binaries) are not in your PATH. If you are going to
> > use
> > /usr/local/lam_mpi/bin/mpicc (mpiCC, mpif77 etc) for
> > compiling MPI
> > programs the you should append
> > /usr/local/lam_mpi/bin to your PATH.
> > After modifying your PATH you might want to do
> > following checks --
> > 1. Invoke 'which mpicc' on the shell to see if you
> > are using right mpicc
> > 2. Invoke 'mpicc --showme' on the shell and check if
> > it uses right set of
> > header and library files. (In your case, you
> > might expect mpicc to use
> > -L/usr/local/lam_mpi/lib and
> > -I/usr/local/lam_mpi/include)
>
>
> Hi LAM developers,
> Here is the result from which mpicc, after the same
> problem with finding mpicc:
>
> checking for mpi.h... no
> configure: error: cannot continue -- cannot find
> <mpi.h>
> :)which mpicc
> /usr/local/lam_mpi/bin/mpicc
>
> Here is the result from invoking mpicc with the
> "showme" option:
>
> :)mpicc --showme
> xlc_r -I/usr/local/lam_mpi/include
> -L/usr/local/lam_mpi/lib -llamf77mpi -lmpi -llam
>
> It looks like it gets the correct include directory,
> but I am not sure if I should add something like -impi
> in a fashion analogous to the -lmpi for the library
> file specification.
> Thanks again,
> Andy
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business $15K Web Design Giveaway
> http://promotions.yahoo.com/design_giveaway/
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
>
|
