octave bug: mkoctfile broken

[ghenshaw@…]

mkoctfile, the octave compiler, appears to be broken. When used to compile an octave script file (such as one of the example files included with octave 2.1.70, hello.cc), mkoctfile returns:

mkoctfile hello.cc

g++-dp-3.4: couldn't run `undle_loader-gcc-3.4.3': No such file or directory

A working mkoctfile is needed in order to install octave-forge and is also useful for speeding up octave script files; without it, octave works but is only suitable for casual use.

I believe this to be a darwinports issue and not an octave issue because other builds of octave 2.1.70 for OSX 10.4 appear to work.

[gwright@…]

I'll take a look at this.

It's a more complicated problem than it looks: the mkoctfile is using apple specific compiler commands. So we need to use an Apple compiler. But we need a fortran to build octave as well, and there are differences between the Apple and FSF compilers. (Differences in the sense of "won't link".) We might need to try to build a fortran from the apple branch. Ugh.

Sometimes we get lucky and sometime not; for a long tim g77 3.3.3 was acceptable but at some point it was no longer possible to link octave using g77 and the default compilers under Xcode.

If you know which fortran is being used with the other 10.4 builds that are available that would be very helpful. The R port is stuck on the same issue. Another thing that would be helpful to know is whether these other builds were built on 10.3 or 10.4. It may be possible to get a build using the Xcode 1.5 tools to work on both platforms.

/gw

[gwright@…]

I just committed a fix and was able to build the hello.cc example using "mkoctfile".

Try it out and let me know if it works for you. If it does, I can clean it up a bit and bump the octave version to 2.1.71.

/gw