I will fix this tomorrow
Right now, --enable-mpi-fortran is --enable-mpi-fortran=yes is --enable-mpi-fortran=all :
So configure aborts if not all bindings can be built
In ompi_configure_options.m4 :
108 case "x$enable_mpi_fortran" in
110 AC_MSG_RESULT([yes (all/default)])
117 AC_MSG_RESULT([yes (all)])
should only happen when xall an not when xyes
I will review this tomorrow,
In the mean time, feel free to revert the changeset or simply not use the --enable-mpi-fortran for now
Ralph Castain <rhc_at_[hidden]> wrote:
>Umm....this really broke things now. I can't build the fortran bindings at all, and I don't have a PGI compiler. I also didn't specify a level of Fortran support, but just had --enable-mpi-fortran
>Maybe we need to revert this commit until we figure out a better solution?
>On Jul 30, 2014, at 12:16 AM, Gilles Gouaillardet <gilles.gouaillardet_at_[hidden]> wrote:
>> this is a fair point.
>> i commited r32354 in order to abort configure in this case
>> On 2014/07/30 15:11, Paul Hargrove wrote:
>>> On a related topic:
>>> I configured with an explicit --enable-mpi-fortran=usempif08.
>>> Then configure found PROCEDURE was missing/broken.
>>> The result is that the build continued, but without the requested f08
>>> If the user has explicitly enabled a given level of Fortran support, but it
>>> cannot be provided, shouldn't this be a configure-time error?
>> devel mailing list
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post: http://www.open-mpi.org/community/lists/devel/2014/07/15352.php
>devel mailing list
>Link to this post: http://www.open-mpi.org/community/lists/devel/2014/07/15357.php