On Nov 27, 2014, at 11:06 PM, Joshua Root wrote: > On 2014-11-28 15:53 , Mihai Moldovan wrote: >> >> The compilers PortGroup is currently only putting library dependencies on >> libgcc. >> >> We hit a bug with octave today, where octave defaults to +gcc48, uses >> fortran. >> but does only build-depend on gcc48. >> >> That's fine when compiling from source (and not using port_cutleaves), but >> will >> fail blatantly when installing from binary archives. In that case, >> libgfortran >> will be missing the package broken. > > Isn't libgfortran meant to be in libgcc?
Not only is it meant to be there, it actually is there: $ port contents libgcc | grep gfortran /opt/local/lib/libgcc/libgfortran.3.dylib _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
