On Jul 5, 2015, at 12:50 PM, Michael Dickens wrote: > I've been working on a fix to this issue, but haven't finalized it yet. > The problem is that mkoctfile hard-codes -L and -I paths, when what it > should actually do is glean them at runtime just before compiling or > linking. My way around this is to override the settings in mkoctfile by > those determined from the active libgcc port. Since all of the gcc4* > ports link with the libraries provided by libgcc, we should not have to > rev-bump octave* ports for updates to gcc4*.
And there would presumably be no difference for gcc5 or gcc6 or later either. _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
