octave-control configure fail

[Michael Dickens]

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*.

All of the above said, I need to get the qt4-mac relocation work done
first. I don't know when I'll get to this item, since I have only so
much free time in July and August for this sort of work. And, doing a
rev-bump is pretty simple in the whole scheme of things, so there does
not seem to be a major need for this work just yet. Thus, adding in the
comment as Ryan says to the top of the Portfile seems like a wise idea.
- MLD

On Sun, Jul 5, 2015, at 12:26 AM, Mihai Moldovan wrote:
> On 05.07.2015 05:46 AM, Ryan Schmidt wrote:
> > If octave truly requires a revbump following every gcc upgrade, that's horrible.
> > 
> > But if that's going to remain the case, then I guess a comment should be added to the top of every affected gcc port reminding us of that.
> 
> It hardcodes gfortran's path (and maybe more?) :(
> 
> So yes, for everything but a revbump of gcc ports, octave must be
> revbumped (and
> maybe even octave-control.)