Jeff Hammond writes:
> Preprocessor is fine in Fortran compilers. We’ve used in NWChem for many
> years, and NWChem supports “all the compilers”.
>
> Caveats:
> - Cray dislikes recursive preprocessing logic that other compilers handle.
> You won’t use this so please ignore.
> - IBM XLF requires -
Preprocessor is fine in Fortran compilers. We’ve used in NWChem for many
years, and NWChem supports “all the compilers”.
Caveats:
- Cray dislikes recursive preprocessing logic that other compilers handle.
You won’t use this so please ignore.
- IBM XLF requires -WF,-DFOO=BAR instead of -DFOO=BAR bu
"Jeff Squyres (jsquyres) via users" writes:
> Hi Dave; thanks for reporting.
>
> Yes, we've fixed this -- it should be included in 4.0.1.
>
> https://github.com/open-mpi/ompi/pull/6121
Good, but I'm confused; I checked the repo before reporting it.
[I wince at processing Fortran with cpp, th
Hi Dave; thanks for reporting.
Yes, we've fixed this -- it should be included in 4.0.1.
https://github.com/open-mpi/ompi/pull/6121
If you care, you can try the nightly 4.0.x snapshot tarball -- it should
include this fix:
https://www.open-mpi.org/nightly/v4.0.x/
> On Dec 4, 2018, at
If you try to build somewhere out of tree, not in a subdir of the
source, the Fortran build is likely to fail because mpi-ext-module.F90
does
include
'/openmpi-4.0.0/ompi/mpiext/pcollreq/mpif-h/mpiext_pcollreq_mpifh.h'
and can exceed the fixed line length. It either needs to add (the
com
