[MacPorts] #57284: arpack links with libgfortran.4.dylib without declaring dependency on libgcc7

[MacPorts]

#57284: arpack links with libgfortran.4.dylib without declaring dependency on
libgcc7
------------------------+----------------------
 Reporter:  ryandesign  |      Owner:  mamoll
     Type:  defect      |     Status:  assigned
 Priority:  Normal      |  Milestone:
Component:  ports       |    Version:
 Keywords:              |       Port:  arpack
------------------------+----------------------
 Building octave-devel fails:

 {{{
 dyld: Library not loaded: /opt/local/lib/libgcc/libgfortran.4.dylib
   Referenced from: /opt/local/lib/libarpack.2.dylib
   Reason: image not found
 /bin/sh: line 1: 32083 Trace/BPT trap: 5       /bin/sh run-octave --norc
 --silent --no-history --path
 /opt/local/var/macports/build/_opt_bblocal_var_buildworker_ports_build_ports_math_octave
 /octave-devel/work/octave-5.0.0/doc/interpreter/ --eval "geometryimages
 ('doc/interpreter/', 'griddata', 'txt');"
 make[2]: *** [doc/interpreter/griddata.txt] Error 133
 }}}

 It appears that libarpack.2.dylib, provided by the arpack port, is linking
 with libgfortran.''4''.dylib, which is provided by the libgcc7 port, but
 it does not declare a dependency on that port. It does declare a
 dependency on gcc8, which has a dependency on libgcc, which has a
 dependency on libgcc8, and libgcc8 provides libgfortran.''5''.dylib. And
 in fact rebuilding arpack makes it relink itself with
 libgfortran.''5''.dylib for me. So maybe the solution is to just increase
 its revision to rebuild it.

 This is probably fallout from when gcc8 was updated to the first stable
 version and libgcc8 was introduced (August 4). arpack probably just hasn't
 had a version or revision increase since then (its last version increase
 was August 1).

-- 
Ticket URL: <https://trac.macports.org/ticket/57284>
MacPorts <https://www.macports.org/>
Ports system for macOS