Hi Jared,
You can add CFLAGS="-I/usr/local/include" to the configure command.
However, since you are just starting out with LAM, I strongly suggest
you spend your time learning Open MPI instead (www.open-mpi.org) . No
development is being done in LAM, and all developers have moved on. The
Open MPI community is very active and happy to assist new-comers.
Cheers,
Mac
Houston
-----Original Message-----
From: lam-bounces_at_[hidden] [mailto:lam-bounces_at_[hidden]] On Behalf
Of Jared Webb
Sent: Wednesday, February 03, 2010 10:46 AM
To: lam_at_[hidden]
Subject: LAM: Test Suite Error
I searched the archives and there was a thread with a similar error back
in 2004, but it didn't seem to apply anymore.
I am just learning how to use mpi. I am running OS X 10.6, I installed
lam and can execute the lamboot command without any trouble.
However, when I try to configure the test suite, I get the following:
bash-3.2$ ls
LICENSE acinclude.m4 config.log env onesided
Makefile.am aclocal.m4 configure group pt2pt
Makefile.in ccl configure.in info
reporting
README comm dtyp io topo
VERSION config dynamic lam
bash-3.2$ ./configure
Configuring LAM test suite version 7.1.4 checking for a BSD-compatible
install... /usr/bin/install -c checking whether build environment is
sane... yes checking for gawk... no checking for mawk... no checking for
nawk... no checking for awk... awk checking whether make sets $(MAKE)...
yes checking build system type... i386-apple-darwin10.2.0 checking host
system type... i386-apple-darwin10.2.0 checking for mpicc... yes
checking for gcc... mpicc checking for C compiler default output file
name... a.out checking whether the C compiler works... yes checking
whether we are cross compiling... no checking for suffix of
executables...
checking for suffix of object files... o checking whether we are using
the GNU C compiler... yes checking whether mpicc accepts -g... yes
checking for mpicc option to accept ANSI C... none needed checking for
style of include used by make... GNU checking dependency style of
mpicc... gcc3 checking for mpic++... yes checking whether we are using
the GNU C++ compiler... yes checking whether mpic++ accepts -g... yes
checking dependency style of mpic++... gcc3 checking for mpif77... yes
checking whether we are using the GNU Fortran 77 compiler... no checking
whether mpif77 accepts -g... no checking for ranlib... ranlib checking
for mpi.h... no
configure: error: cannot continue -- cannot find <mpi.h>
The other thread I saw from 2004 said to check to make sure that mpi.h
was in my path. I found mpi.h in /usr/local/include and added that to
my path, but the same error occurs. Am I missing anything obvious?
Thanks for your help
_______________________________________________
This list is archived at http://www.lam-mpi.org/MailArchives/lam/
.
|
