[MacPorts] #39365: arpack @3.1.1 +openmpi or +mpich configure fails if mpi wasn't built with fortran wrappers
MacPorts
noreply at macports.org
Thu Jun 6 13:23:11 PDT 2013
#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: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.3
Keywords: haspatch | Port: arpack
------------------------+--------------------------------
The variants +openmpi or +mpich make the build fail if openmpi/mpich were
not built with Fortran support, since configure cannot find (open)mpif77.
We should use active_variants to make sure the dependency was built with
Fortran support, and indeed it probably needs to be the same Fortran
compiler as is being used for F77.
A more minor issue: building with MPI causes some PARPACK test programs to
be installed.
{{{
Port arpack contains:
/opt/local/bin/pcndrv1
/opt/local/bin/pdndrv1
/opt/local/bin/pdndrv3
/opt/local/bin/pdsdrv1
/opt/local/bin/psndrv3
/opt/local/bin/pssdrv1
/opt/local/bin/pzndrv1
...
}}}
By analogy to the ARPACK test program {{{dnsimp}}}, these should probably
not be installed. They don't work anyway, for me at least, even though
PARPACK works fine in an application.
{{{
$ pcndrv1
dyld: lazy symbol binding failed: Symbol not found: _second_
Referenced from: /opt/local/lib/libparpack.2.dylib
Expected in: flat namespace
dyld: Symbol not found: _second_
Referenced from: /opt/local/lib/libparpack.2.dylib
Expected in: flat namespace
Trace/BPT trap: 5
}}}
Attached Portfile diff establishes active variants requirements and
removes test programs from installation.
Also, it seems from livecheck that arpack 3.1.3 has been released, so I
guess that could be updated in the port.
--
Ticket URL: <https://trac.macports.org/ticket/39365>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list