Re: [OMPI devel] openmpi 3.1.x examples

2018-07-17 Thread Jeff Squyres (jsquyres) via devel
On Jul 17, 2018, at 1:18 AM, Marco Atzeri  wrote:
> 
> I was aware, as I am not building it anymore, however
> probably we should exclude the C++ from default examples.

examples/Makefile won't build the C++ (or Fortran or OSHMEM) examples if they 
aren't built.

My $0.02: As long as we're shipping the C++ bindings -- even if you have to 
turn them on manually -- we should still ship the C++ examples.

-- 
Jeff Squyres
jsquy...@cisco.com

___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel


Re: [OMPI devel] openmpi 3.1.x examples

2018-07-17 Thread Nathan Hjelm via devel


> On Jul 16, 2018, at 11:18 PM, Marco Atzeri  wrote:
> 
>> Am 16.07.2018 um 23:05 schrieb Jeff Squyres (jsquyres) via devel:
>>> On Jul 13, 2018, at 4:35 PM, Marco Atzeri  wrote:
>>> 
 For one. The C++ bindings are no longer part of the standard and they are 
 not built by default in v3.1x. They will be removed entirely in Open MPI 
 v5.0.0.
>> Hey Marco -- you should probably join our packagers mailing list:
>> https://lists.open-mpi.org/mailman/listinfo/ompi-packagers
>> Low volume, but intended exactly for packagers like you.  It's fairly 
>> recent; we realized we needed to keep in better communication with our 
>> downstream packagers.
> 
> noted thanks.
> 
>> (+ompi-packagers to the CC)
>> As Nathan mentioned, we stopped building the MPI C++ bindings by default in 
>> Open MPI 3.0.  You can choose to build them with the configure 
>> --enable-mpi-cxx.
> 
> I was aware, as I am not building it anymore, however
> probably we should exclude the C++ from default examples.

Good point. I will fix that today and PR the fix to v3.0.x and v3.1.x. 


> Regards
> Merco
> 
> ---
> Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
> https://www.avast.com/antivirus
> 
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/devel
___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel

Re: [OMPI devel] openmpi 3.1.x examples

2018-07-16 Thread Marco Atzeri

Am 16.07.2018 um 23:05 schrieb Jeff Squyres (jsquyres) via devel:

On Jul 13, 2018, at 4:35 PM, Marco Atzeri  wrote:



For one. The C++ bindings are no longer part of the standard and they are not 
built by default in v3.1x. They will be removed entirely in Open MPI v5.0.0.


Hey Marco -- you should probably join our packagers mailing list:

 https://lists.open-mpi.org/mailman/listinfo/ompi-packagers

Low volume, but intended exactly for packagers like you.  It's fairly recent; 
we realized we needed to keep in better communication with our downstream 
packagers.



noted thanks.


(+ompi-packagers to the CC)

As Nathan mentioned, we stopped building the MPI C++ bindings by default in 
Open MPI 3.0.  You can choose to build them with the configure --enable-mpi-cxx.


I was aware, as I am not building it anymore, however
probably we should exclude the C++ from default examples.

Regards
Merco

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus

___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel

Re: [OMPI devel] openmpi 3.1.x examples

2018-07-16 Thread Jeff Squyres (jsquyres) via devel
On Jul 13, 2018, at 4:35 PM, Marco Atzeri  wrote:
> 
>> For one. The C++ bindings are no longer part of the standard and they are 
>> not built by default in v3.1x. They will be removed entirely in Open MPI 
>> v5.0.0.

Hey Marco -- you should probably join our packagers mailing list:

https://lists.open-mpi.org/mailman/listinfo/ompi-packagers

Low volume, but intended exactly for packagers like you.  It's fairly recent; 
we realized we needed to keep in better communication with our downstream 
packagers.

(+ompi-packagers to the CC)

As Nathan mentioned, we stopped building the MPI C++ bindings by default in 
Open MPI 3.0.  You can choose to build them with the configure --enable-mpi-cxx.

This is the current plan:

- In v4.0, we're no longer building a bunch of other deleted MPI-1 functions by 
default (which can be restored via --enable-mpi1-compat, and --enable-mpi-cxx 
will still work).

- In v5.0, delete all the C++ bindings and the deleted MPI-1 functions.

-- 
Jeff Squyres
jsquy...@cisco.com

___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel


Re: [OMPI devel] openmpi 3.1.x examples

2018-07-13 Thread Marco Atzeri

Am 13.07.2018 um 22:07 schrieb Nathan Hjelm via devel:

For one. The C++ bindings are no longer part of the standard and they are not 
built by default in v3.1x. They will be removed entirely in Open MPI v5.0.0.

Not sure why the fortran one is not building.



the fortran problem is due to a compiler settings
It works with

$ mpifort -g  hello_usempi.f90  -o hello_usempi -fintrinsic-modules-path 
/usr/lib


---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com

___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel

Re: [OMPI devel] openmpi 3.1.x examples

2018-07-13 Thread Nathan Hjelm via devel
For one. The C++ bindings are no longer part of the standard and they are not 
built by default in v3.1x. They will be removed entirely in Open MPI v5.0.0. 

Not sure why the fortran one is not building. 

-Nathan

> On Jul 13, 2018, at 2:02 PM, Marco Atzeri  wrote:
> 
> Hi,
> may be I am missing something obvious, but are the
> examples still actual
> 
>  C:   hello_c.c
>  C++: hello_cxx.cc
>  Fortran mpif.h:  hello_mpifh.f
>  Fortran use mpi: hello_usempi.f90
>  Fortran use mpi_f08: hello_usempif08.f90
>  Java:Hello.java
>  C shmem.h:   hello_oshmem_c.c
>  Fortran shmem.fh:hello_oshmemfh.f90
> 
> 
> $ make hello_cxx
> mpic++ -g  hello_cxx.cc  -o hello_cxx
> hello_cxx.cc: In function ‘int main(int, char**)’:
> hello_cxx.cc:25:5: error: ‘MPI’ has not been declared
> 
> $ make -i
> ...
> mpifort -g  hello_usempi.f90  -o hello_usempi
> hello_usempi.f90:14:8:
> 
> use mpi
>1
> Fatal Error: Can't open module file ‘mpi.mod’ for reading at (1): No such 
> file or directory
> 
> The second could be a different problem
> 
> $ ls /usr/lib/mpi.mod
> /usr/lib/mpi.mod
> 
> 
> ---
> Diese E-Mail wurde von AVG auf Viren geprüft.
> http://www.avg.com
> 
> ___
> devel mailing list
> devel@lists.open-mpi.org
> https://lists.open-mpi.org/mailman/listinfo/devel
___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel

[OMPI devel] openmpi 3.1.x examples

2018-07-13 Thread Marco Atzeri

Hi,
may be I am missing something obvious, but are the
examples still actual

  C:   hello_c.c
  C++: hello_cxx.cc
  Fortran mpif.h:  hello_mpifh.f
  Fortran use mpi: hello_usempi.f90
  Fortran use mpi_f08: hello_usempif08.f90
  Java:Hello.java
  C shmem.h:   hello_oshmem_c.c
  Fortran shmem.fh:hello_oshmemfh.f90


$ make hello_cxx
mpic++ -g  hello_cxx.cc  -o hello_cxx
hello_cxx.cc: In function ‘int main(int, char**)’:
hello_cxx.cc:25:5: error: ‘MPI’ has not been declared

$ make -i
...
mpifort -g  hello_usempi.f90  -o hello_usempi
hello_usempi.f90:14:8:

 use mpi
1
Fatal Error: Can't open module file ‘mpi.mod’ for reading at (1): No 
such file or directory


The second could be a different problem

$ ls /usr/lib/mpi.mod
/usr/lib/mpi.mod


---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com

___
devel mailing list
devel@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/devel