configury: always require Python for building Open MPI #13254
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See individual commit messages for details. The main / important commit in this PR has the following commit message:
Commit cb4fe48 didn't quite get the Python configury tests correct. This commit fixes several issues:
Move the AM_INIT_AUTOMAKE up before we call AM_PATH_PYTHON.
Since we converted a few Perl scripts to Python in a60b03b, we now always need Python to build Open MPI. Multiple Python scripts are invoked post-configure (i.e., reacting to configure results -- see a60b03b) to build the C and Fortran and MPI bindings.
Since we now always have Python, remove the OMPI_GENERATE_BINDINGS AM_CONDITIONAL.
Use the slightly-more-correct
$(PYTHON)
in Makefile.am (vs.$(python)
).