Re: octave-control configure fail

Yes, there would be no difference so long as gcc5+ uses libgcc or libgcc-devel (which they seem to do). The change actually works pretty well in my testing; in the pre-configure stage from octave-1.0.tcl, change the current "configure.env-append" to instead do: {{{ set GFORTRAN [glob ${prefix}/

Re: octave-control configure fail

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 th

Re: octave-control configure fail

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 determine

Re: octave-control configure fail

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

Re: octave-control configure fail

On Jul 4, 2015, at 10:28 AM, Mihai Moldovan wrote: > On 04.07.2015 04:34 PM, Marius Schamschula wrote: >> That means octave was not revision bumped with the gcc48 update. You’ll need >> to >> rebuild octave. >> >> As gcc49 was also updated recently, octave will need to be rev-bumped. You >> sh

Re: octave-control configure fail

> On Jul 4, 2015, at 11:28 AM, Mihai Moldovan wrote: > > On 04.07.2015 04:34 PM, Marius Schamschula wrote: >> That means octave was not revision bumped with the gcc48 update. You’ll need >> to >> rebuild octave. >> >> As gcc49 was also updated recently, octave will need to be rev-bumped. You

Re: octave-control configure fail

On 04.07.2015 04:34 PM, Marius Schamschula wrote: > That means octave was not revision bumped with the gcc48 update. You’ll need > to > rebuild octave. > > As gcc49 was also updated recently, octave will need to be rev-bumped. You > should add a ticket on MacPorts trac. Revbumped in https://tra

Re: octave-control configure fail

Alan, That means octave was not revision bumped with the gcc48 update. You’ll need to rebuild octave. As gcc49 was also updated recently, octave will need to be rev-bumped. You should add a ticket on MacPorts trac. On Jul 4, 2015, at 9:27 AM, Alan Rakes wrote: > > Unfortunately, I still go

Re: octave-control configure fail

> On Jul 4, 2015, at 9:50 AM, Marius Schamschula wrote: > > Alan, > > On Jul 4, 2015, at 8:45 AM, Alan Rakes > wrote: > >>> >>> On Jul 4, 2015, at 9:34 AM, Marius Schamschula >> > wrote: >>> >>> Alan, >>> >>> On Jul 4, 2015, at 8:

Re: octave-control configure fail

Alan, On Jul 4, 2015, at 8:45 AM, Alan Rakes wrote: >> >> On Jul 4, 2015, at 9:34 AM, Marius Schamschula wrote: >> >> Alan, >> >> On Jul 4, 2015, at 8:29 AM, Alan Rakes wrote: >> >>> I’ve been on Yosemite ever since I set up macports. I just updated to >>> 10.10.4, but this happened two

Re: octave-control configure fail

> On Jul 4, 2015, at 9:34 AM, Marius Schamschula wrote: > > Alan, > > On Jul 4, 2015, at 8:29 AM, Alan Rakes > wrote: > >> I’ve been on Yosemite ever since I set up macports. I just updated to >> 10.10.4, but this happened two days ago before I made that change

Re: octave-control configure fail

Alan, On Jul 4, 2015, at 8:29 AM, Alan Rakes wrote: > I’ve been on Yosemite ever since I set up macports. I just updated to > 10.10.4, but this happened two days ago before I made that change so I don’t > think that is it. I don’t know why it is trying to use gcc 4.8 here. Here > are the v

Re: octave-control configure fail

I’ve been on Yosemite ever since I set up macports. I just updated to 10.10.4, but this happened two days ago before I made that change so I don’t think that is it. I don’t know why it is trying to use gcc 4.8 here. Here are the versions of gcc I have installed. gcc48 @4.8.4_0 gcc48 @4.8.

Re: octave-control configure fail

Alan, On Jul 4, 2015, at 8:06 AM, Alan Rakes wrote: > During a routine sudo port upgrade outdated, I started getting a configure > error on upgrading octave-control. I performed a sudo port clean > octave-control and tried again which often works, but this time, alas no. > > Here is the mess

octave-control configure fail

During a routine sudo port upgrade outdated, I started getting a configure error on upgrading octave-control. I performed a sudo port clean octave-control and tried again which often works, but this time, alas no. Here is the message when it failed. Error: org.macports.configure for port octav