libgcc-devel does not provide libgforgran

[michaelld (Michael Dickens)]

The current libgcc does provide libgfortran, while at least my local build of libgcc-devel does not, which messes up a handful of ports that need Fortran. Is this a feature or a bug? I've attached the install log if that helps.

$ sudo port -f uninstall libgcc-devel
$ sudo port clean libgcc-devel
$ sudo port -k install libgcc-devel
--->  Computing dependencies for libgcc-devel
--->  Fetching distfiles for libgcc-devel
--->  Verifying checksums for libgcc-devel
--->  Extracting libgcc-devel
--->  Configuring libgcc-devel
--->  Building libgcc-devel
--->  Staging libgcc-devel into destroot
--->  Installing libgcc-devel @7-20161030_0
--->  Activating libgcc-devel @7-20161030_0
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found.                             

$ port contents libgcc-devel
Port libgcc-devel contains:
  /opt/local/lib/libgcc/libatomic.1.dylib
  /opt/local/lib/libgcc/libgcc_ext.10.4.dylib
  /opt/local/lib/libgcc/libgcc_ext.10.5.dylib
  /opt/local/lib/libgcc/libgcc_s.1.dylib
  /opt/local/lib/libgcc/libgomp.1.dylib
  /opt/local/lib/libgcc/libitm.1.dylib
  /opt/local/lib/libgcc/libobjc-gnu.4.dylib
  /opt/local/lib/libgcc/libquadmath.0.dylib
  /opt/local/lib/libgcc/libssp.0.dylib
  /opt/local/lib/libgcc/libstdc++.6.dylib
  /opt/local/lib/libstdc++.6.dylib

[michaelld (Michael Dickens)]

Attachment is too big. Here's a link to it: ​https://www.dropbox.com/s/6jacqrxf8oowvn8/libgcc-devel_7-20161030_0.log?dl=0 .

"uname -a" returns "Darwin mld-mbpr-10-12 16.1.0 Darwin Kernel Version 16.1.0: Thu Oct 13 21:26:57 PDT 2016; root:xnu-3789.21.3~60/RELEASE_X86_64 x86_64" if that helps.

[michaelld (Michael Dickens)]

FYI that libgcc-devel @20161106_0 still does not provide this library, at least for me.

[michaelld (Michael Dickens)]

Has duplicate, showing symptoms of the issue here, in ticket #52834.

[michaelld (Michael Dickens)]

libgcc-devel @7-20161225_0 fixes this issue, providing "libgfortran.4.dylib" ... which is different than the prior "libgfortran.3.dylib" so I'd guess many Fortran dependent ports will require a rev-bump. I'm going to close this ticket as fixed.