Re: macOS 4.4.0 DMG (beta2) ready for testing

[Andrew Janke]

On 7/16/18 4:49 PM, Mike Miller wrote:
> [...]
> This error has come up before a few times over the past couple years,
> always when installing the control package, and only on macOS systems.
>
> The "<built-in>" tag is coming from the gfortran compiler itself. I
> suspect it is referring to built-in Fortran functions.
>
> The control package is one of the few Octave Forge packages that has
> Fortran source code that is compiled by the pkg command when installed.
>
> Here are some references to threads and bug reports where this has come
> up before, maybe this will help you resolve this or help users fix it
> when it comes up again.
>
> https://savannah.gnu.org/bugs/?48625
> https://savannah.gnu.org/bugs/?49236
> http://octave.1599824.n4.nabble.com/Control-3-0-0-won-t-install-td4682447.html
> https://savannah.gnu.org/bugs/?50886
> http://octave.1599824.n4.nabble.com/Mac-OS-install-control-pkg-3-1-0-td4687497.html
Thanks Mike; that's very helpful. It looks like not only is it only on 
macOS systems, but only
with the Octave.app distribution. It sounds like our gfortran build has 
an issue. We are attempting
to be conservative and build a Core2 gcc/gfortran by passing 
"-march=core2" to everything,
but maybe that's not working for gfortran.

sshah, can you try this:

Point Octave.app at your Homebrewed gfortran, instead of its own, and 
try installing control again:

setenv('F77', '/usr/local/bin/gfortran')
pkg install -forge control

If that still gives you an error, try locally rebuilding your Homebrewed 
gcc from source, and
use that:

In the shell:
$ brew reinstall -s gcc

In Octave.app:
setenv('F77', '/usr/local/bin/gfortran')
pkg install -forge control

Cheers,
Andrew