Re: [OMPI devel] openmpi 3.1.x examples
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] Cygwin Fortran compiler options
Am 16.07.2018 um 23:06 schrieb Jeff Squyres (jsquyres) via devel: Split the Fortran issue off into its own thread (and kept it on devel; no need for ompi-packagers) On Jul 13, 2018, at 4:35 PM, Marco Atzeri wrote: 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 Should we add something to configure to detect/use this flag automatically? no, I think it is a issue of latest fortran compiler in cygwin; I am sure it was not like that with previous version. I also noted that also in this ways works $ mpifort -g hello_usempi.f90 -o hello_usempi -I /usr/lib probably some default changed between gcc 6.3 and 7.3 Regards Marco --- 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
[OMPI devel] Cygwin Fortran compiler options (was: openmpi 3.1.x examples)
Split the Fortran issue off into its own thread (and kept it on devel; no need for ompi-packagers) On Jul 13, 2018, at 4:35 PM, Marco Atzeri wrote: > > 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 Should we add something to configure to detect/use this flag automatically? -- 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
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
