[MacPorts] #39365: arpack @3.1.1 +openmpi or +mpich configure fails if mpi wasn't built with fortran wrappers

[MacPorts]

#39365: arpack @3.1.1 +openmpi or +mpich configure fails if mpi wasn't built with
fortran wrappers
-------------------------+--------------------------------
  Reporter:  dstrubbe@…  |      Owner:  macports-tickets@…
      Type:  defect      |     Status:  reopened
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.1.3
Resolution:              |   Keywords:  haspatch
      Port:  arpack      |
-------------------------+--------------------------------
Changes (by dstrubbe@…):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I found workarounds to the 3.1.3 issues. See attached Portfile patch,
 which updates to 3.1.3. Basically, we need to use the '-l' style of
 linking for blas/lapack.

 I removed g95 which no longer works with this version. Before, the linking
 happened with the C compiler, but now the Fortran one has to do it, and
 g95 won't accept the link options given by libtool in arpack.

 Previously, you could select independently the Fortran compiler and the
 MPI implementation. However, we enforced that the MPI had to have been
 built with the corresponding compiler. In fact, doing that implies there
 is no purpose in specifying the Fortran compiler when using MPI, so I made
 openmpi and mpich variants on the same footing as the Fortran compilers,
 all conflicting. This could have been done in the 3.1.2 Portfile too, but
 it is necessary now for 3.1.3, because if we specify F77 with the Fortran
 compiler as we were doing, then that will be used to link, which will fail
 in PARPACK. We must give (open)mpif77 as F77 to make it work, in which
 case gfortran has no role to play any more. We must still enforce that
 some Fortran wrapper is present for the MPI ports, so I added that to the
 pre-fetch stage.

 The gcc variants use 'configure.compiler' rather than setting F77
 explicitly. This makes sure that compiler suite used also for C checks in
 the configure script.

-- 
Ticket URL: <https://trac.macports.org/ticket/39365#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X