Re: [OMPI users] mpicc -showme:compile output (possible bug report)

[Crni Gorac]

On Thu, Apr 17, 2008 at 6:36 AM, Terry Frankcombe  wrote:
> Given that discussion, might I suggest an (untested) workaround would be
>  to --prefix OpenMPI into a non-standard location?

It is possible approach, but there are others - it is also possible to
provide specific CMake variable value on CMake command line, and it
will find OpenMPI fine then.  But both are kind of hassle, it is of
course perfectly normal to install OpenMPI to usual locations, and
given comments above, I'm inclined to think that OpenMPI behavior, in
not printing "-I" and "-L" flags on "-showme:compile" and
"-showme:link", is actually desired here.  So this probably should be
classified as CMake bug.

Regards.

Re: [OMPI users] mpicc -showme:compile output (possible bug report)

[Terry Frankcombe]

Given that discussion, might I suggest an (untested) workaround would be
to --prefix OpenMPI into a non-standard location?



On Wed, 2008-04-16 at 13:03 -0400, Jeff Squyres wrote:
> On Apr 16, 2008, at 9:38 AM, Crni Gorac wrote:
> >> mpicc (and friends) typically do not output -I only for "special"
> >> directories, such as /usr/include, because adding -I/usr/include may
> >> subvert the compiler's normal include directory search order.
> >
> > On my machine, "mpicc -showme:compile" outputs  "-pthread" only.
> 
> This would seem to indicate that OMPI is specifically choosing not to  
> display the -I/whatever flag, most likely because it would have been - 
> I/usr/include (or similar).
> 
> > I guess CMake is modeling MPI recognizing after MPICH, and that "-I"
> > flags appears in "mpicc -showme:compile" output there; tried to check
> > that, but latest MPICH (1.0.7) won't even compile on my machine...  In
> > any case, I reported the issue to the CMake bug tracker too.
> 
> 
> Ok.  If OMPI is installed with a prefix of /usr, I don't anticipate us  
> changing this behavior -- this exception is specifically implemented  
> to not subvert the normal compiler include directory search order.   
> Note, too, that the same issue will occur with -L in the --showme:link  
> line -- we don't display -L/usr/lib for the same reasons as described  
> above.
> 

Re: [OMPI users] mpicc -showme:compile output (possible bug report)

[Jeff Squyres]

On Apr 16, 2008, at 9:38 AM, Crni Gorac wrote:

mpicc (and friends) typically do not output -I only for "special"
directories, such as /usr/include, because adding -I/usr/include may
subvert the compiler's normal include directory search order.


On my machine, "mpicc -showme:compile" outputs  "-pthread" only.


This would seem to indicate that OMPI is specifically choosing not to  
display the -I/whatever flag, most likely because it would have been - 
I/usr/include (or similar).



I guess CMake is modeling MPI recognizing after MPICH, and that "-I"
flags appears in "mpicc -showme:compile" output there; tried to check
that, but latest MPICH (1.0.7) won't even compile on my machine...  In
any case, I reported the issue to the CMake bug tracker too.



Ok.  If OMPI is installed with a prefix of /usr, I don't anticipate us  
changing this behavior -- this exception is specifically implemented  
to not subvert the normal compiler include directory search order.   
Note, too, that the same issue will occur with -L in the --showme:link  
line -- we don't display -L/usr/lib for the same reasons as described  
above.


--
Jeff Squyres
Cisco Systems

Re: [OMPI users] mpicc -showme:compile output (possible bug report)

[Crni Gorac]

On Wed, Apr 16, 2008 at 2:18 PM, Jeff Squyres  wrote:
> What exactly does mpicc --showme:compile output?
>
>  mpicc (and friends) typically do not output -I only for "special"
>  directories, such as /usr/include, because adding -I/usr/include may
>  subvert the compiler's normal include directory search order.

On my machine, "mpicc -showme:compile" outputs  "-pthread" only.

I guess CMake is modeling MPI recognizing after MPICH, and that "-I"
flags appears in "mpicc -showme:compile" output there; tried to check
that, but latest MPICH (1.0.7) won't even compile on my machine...  In
any case, I reported the issue to the CMake bug tracker too.

Regards.

Re: [OMPI users] mpicc -showme:compile output (possible bug report)

[Jeff Squyres]

What exactly does mpicc --showme:compile output?

mpicc (and friends) typically do not output -I only for "special"  
directories, such as /usr/include, because adding -I/usr/include may  
subvert the compiler's normal include directory search order.



On Apr 16, 2008, at 7:57 AM, Crni Gorac wrote:

Am using CMake build system along with an OpenMPI based project.
CMake is using mpicc's -showme:compile and -showme:link output to
build compile and link flags; however, it is expecting -showme:compile
to dump at least some "-I" flags, that it is further parsing in order
to build the list of include directories.  As OpenMPI's mpicc (OpenMPI
compiled from source on a Slackware Linux 12.0 installation) is not
printing alike flags, CMake is unable to utilize OpenMPI.  So, I'm
wondering would it be possible to change OpenMPI to dump the path to
the directory where mpi.h installed in an "-I" flag, when mpicc
-showme:compile command run?

Thanks.
___
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users



--
Jeff Squyres
Cisco Systems

[OMPI users] mpicc -showme:compile output (possible bug report)

[Crni Gorac]

Am using CMake build system along with an OpenMPI based project.
CMake is using mpicc's -showme:compile and -showme:link output to
build compile and link flags; however, it is expecting -showme:compile
to dump at least some "-I" flags, that it is further parsing in order
to build the list of include directories.  As OpenMPI's mpicc (OpenMPI
compiled from source on a Slackware Linux 12.0 installation) is not
printing alike flags, CMake is unable to utilize OpenMPI.  So, I'm
wondering would it be possible to change OpenMPI to dump the path to
the directory where mpi.h installed in an "-I" flag, when mpicc
-showme:compile command run?

Thanks.