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

2008-04-16 Thread 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.


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

2008-04-16 Thread 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



Re: [OMPI users] open mpi on smp

2008-04-16 Thread Jozef Káčer
I think that in pure OpenMPI environment (without any resorce manager) you
should be able to run applications like this:

mpirun -np 2 mpi_executable
or
mpirun -np 4 -machinefile machines.list mpi_executable

where machines.list contains a list of your computers identified by their
host names.
The former command should run the program locally on 2 processors/cores, the
latter
one on those specified in the list.

Regards,
Jozef

On Tue, Apr 15, 2008 at 6:38 PM, Cally K  wrote:

> hi, am beginner in openmpi
>
>
> could anyone tell me how do i run programs in open mpi on smp.. as in do I
> have to do any changes in hostfile ... like in mpich -- I write
>
> server:2
>
> how do I do it openmpi
>
>
> ___
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>


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

2008-04-16 Thread 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] open mpi on smp

2008-04-16 Thread Mark Kosmowski
Cally:

In the hostfile you add a "slots" line.  For example on my dual
opteron (single core) system, I have slots=2.  This can be read about
in more detail in the FAQ - I provide a link for this section below -
you may need to scroll down to see the example hostfile at the end of
the section.

http://www.open-mpi.org/faq/?category=running#mpirun-scheduling

Happy computing,

Mark Kosmowski

> Message: 1
> Date: Wed, 16 Apr 2008 14:32:58 +0200
> From: " Jozef K??er " 
> Subject: Re: [OMPI users] open mpi on smp
> To: "Open MPI Users" 
> Message-ID:
><8803b3d0804160532t60d9e82embeb01b8389416...@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I think that in pure OpenMPI environment (without any resorce manager) you
> should be able to run applications like this:
>
> mpirun -np 2 mpi_executable
> or
> mpirun -np 4 -machinefile machines.list mpi_executable
>
> where machines.list contains a list of your computers identified by their
> host names.
> The former command should run the program locally on 2 processors/cores, the
> latter
> one on those specified in the list.
>
> Regards,
> Jozef
>
> On Tue, Apr 15, 2008 at 6:38 PM, Cally K  wrote:
>
> > hi, am beginner in openmpi
> >
> >
> > could anyone tell me how do i run programs in open mpi on smp.. as in do I
> > have to do any changes in hostfile ... like in mpich -- I write
> >
> > server:2
> >
> > how do I do it openmpi
> >
> >
> > ___
> > users mailing list
> > us...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/users
> >


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

2008-04-16 Thread 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