Hi,
Today I had the same problem with the tarball lam-7.0.tar.gz from the
LAM home-page. No special options to
configure --with-rsh="ssh -x"
So the prefix is just /usr/local/.
wjmb_at_pchela:~ $ mpiCC -showme
g++ -I/usr/local/include -pthread -L/usr/local/lib -llammpio
-llammpi++ -llamf77mpi -lmpi -llam -lutil -pthread
I don't know if this is how it should be, but it resulted in including some
headers that shouldn't have been there in the first place. Throwing them out
got me on track again.
What I was wondering about after reading this thread: what is incdir?
Regards,
Wouter Brok.
On Mon, Sep 15, 2003 at 10:27:29AM -0500, Arun Rodrigues wrote:
> > On Mon, 15 Sep 2003, Arun Rodrigues wrote:
> >
> > > mpic++ adds "-I/usr/local/include" to the search path. On g++ 3.1 on
> > > MacOS X, this generates the unsightly compiler warning:
> >
> > Which version of LAM are you using?
>
> Whoops, sorry, forgot to mention that.
>
> I am using LAM 7.0, installed from the MacOS X binaries (.dmg)
>
> LAM 7.0/MPI 2 C++/ROMIO - Indiana University
>
> Arch: powerpc-apple-darwin6.6
> Prefix: /usr/local
> Configured by: brbarret
> Configured on: Tue Jul 1 08:28:06 PDT 2003
> Configure host: fluffy.local.
> SSI rpi: crtcp lamd sysv tcp usysv
>
>
> > Recent versions should do a string compare and explicitly *not* add a -I
> > flag if the incdir is /usr/local/include. I don't know exactly what
> > version we started doing that, but it should be this way in 7.0. If it is
> > adding it anyway, it's a bug.
>
> Strange. I did upgrade from 6.5 recently, having noted the same behavior
> there. The mpic++ binary appears to be the correct one:
>
> ls -l /usr/local/bin/mpic++
> -rwxr-xr-x 1 root wheel 403332 Jul 1 10:56 /usr/local/bin/mpic++
>
>
> thanks,
>
> arun
>
>
> -----------------------------------
> Arun Rodrigues *
> http://www.nd.edu/~arodrig6 *
> -----------------------------------
> _______________________________________________
> This list is archived at http://www.lam-mpi.org/MailArchives/lam/
|