Skip to content

v4.0.x: Fortran fixes #7360

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 9, 2020

Conversation

jsquyres
Copy link
Member

@jsquyres jsquyres commented Feb 4, 2020

This is a cherry pick of PR #7265 to the v4.0.x branch.

See the individual commit messages for details.

Unfortunately, right before #7265 was merged, a 3rd commit was squashed incorrectly: one of the two remaining commits has a few hunks that really should have been squashed in to the other commit. Doh.

Refs #7253

These -D's are for C compilation, not Fortran compilation.  Remove
this useless statement.

Signed-off-by: Jeff Squyres <[email protected]>
(cherry picked from commit f4a47a5)
Automake's Fortran compilation rules inexplicably use CPPFLAGS and
AM_CPPFLAGS.  Unfortunately, this can cause problems in some cases
(e.g., picking up already-installed mpi.mod in a system-default
include search path).

So in relevant module-using Fortran compilation Makefile.am's, zero
out CPPFLAGS and AM_CPPFLAGS.

This has a side-effect of requiring that we compile the one .c file in
the F08 library in a new, separate subdirectory (with its own
Makefile.am that does _not_ have CPPFLAGS/AM_CPPFLAGS zeroed out).

Signed-off-by: Jeff Squyres <[email protected]>
Signed-off-by: Gilles Gouaillardet <[email protected]>
(cherry picked from commit ab398f4)
@jsquyres jsquyres added this to the v4.0.3 milestone Feb 4, 2020
@jsquyres
Copy link
Member Author

jsquyres commented Feb 4, 2020

@jeffhammond @marmistrz Can you guys try out this PR? It's a port from master, but master has diverged a bit from the v4.0.x Fortran support -- it would be helpful if you guys could test this one and see if it fixes the problem correctly on the v4.0.x branch. Thanks!

@jsquyres jsquyres added the NEWS label Feb 4, 2020
@jeffhammond
Copy link
Contributor

This also builds without error.

@jsquyres jsquyres requested a review from hppritcha February 7, 2020 18:41
@jsquyres
Copy link
Member Author

jsquyres commented Feb 7, 2020

@gpaulsen @hppritcha This one is all ready to go, if you're still accepting things for v4.0.3. It just needs a review. I'm guessing @ggouaillardet is busy these days...

@hppritcha hppritcha merged commit 42acf4f into open-mpi:v4.0.x Feb 9, 2020
ggouaillardet added a commit to ggouaillardet/ompi that referenced this pull request Apr 14, 2020
An incorrect backport in open-mpi#7360 removed
constants.c from ompi/mpi/fortran/use-mpi-f08/base/Makefile.am

This one off commit fixes that, and move constants.h from
ompi/mpi/fortran/use-mpi-f08 to ompi/mpi/fortran/use-mpi-f08/base

Fixes open-mpi#7616

Signed-off-by: Gilles Gouaillardet <[email protected]>
cniethammer pushed a commit to cniethammer/ompi that referenced this pull request May 10, 2020
An incorrect backport in open-mpi#7360 removed
constants.c from ompi/mpi/fortran/use-mpi-f08/base/Makefile.am

This one off commit fixes that, and move constants.h from
ompi/mpi/fortran/use-mpi-f08 to ompi/mpi/fortran/use-mpi-f08/base

Fixes open-mpi#7616

Signed-off-by: Gilles Gouaillardet <[email protected]>
@jsquyres jsquyres deleted the pr/v4.0.x/fortran-you-win-again branch July 17, 2022 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants