In mpic++_wrapper-data.txt what do the following statments mean and where do
they exactly point to??
----------
includedir=${includedir}
libdir=${libdir}
----------
--- On Tue, 9/23/08, Jeff Squyres <jsquy...@cisco.com> wrote:
From: Jeff Squyres <jsquy...@cisco.com>
Subject: Re: [OMPI users] where is mpif.h ?
To: "Open MPI Users" <us...@open-mpi.org>
List-Post: users@lists.open-mpi.org
Date: Tuesday, September 23, 2008, 5:11 AM
It actually is expected behavior. Open MPI's wrappers do not
automatically add -I for /usr/include or -L for /usr/lib because these
directories are typically in the compiler's/linker's default search
path, and having the wrapper compilers manually add them tends to
screw up search ordering.
You can change the default behavior of the wrapper compilers, though
-- see this FAQ entry for details:
http://www.open-mpi.org/faq/?category=mpi-apps#override-wrappers-after-v1.0
On Sep 23, 2008, at 6:40 AM, Jed Brown wrote:
> On Tue 2008-09-23 08:50, Simon Hammond wrote:
>> Yes, it should be there.
>
> Shouldn't the path be automatically included by the mpif77 wrapper? I
> ran into this problem when building BLACS (my default OpenMPI 1.2.7
> lives in /usr, MPICH2 is at /opt/mpich2). The build tries
>
> $ /usr/bin/mpif90 -c -I. -fPIC -Wno-unused-variable -g
> bi_f77_mpi_attr_get.f
> Error: Can't open included file 'mpif.h'
>
> but this succeeds
>
> $ /usr/bin/mpif90 -c -I. -I/usr/include -fPIC -Wno-unused-variable
> -g bi_f77_mpi_attr_get.f
>
> and this works fine as well
>
> $ /opt/mpich2/mpif90 -c -I. -fPIC -Wno-unused-variable -g
> bi_f77_mpi_attr_get.f
>
> Is this the expected behavior?
>
> Jed
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
Cisco Systems
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
