BUG: octave-2.1.72 AND gcc-4.0.3

[adfernandes (Andrew Fernandes)]

The command "g++-dp-4.0 -bundle -bundle_loader [...]" is incorrectly parsed by DP's gcc.

[adfernandes (Andrew Fernandes)]

When using "mkoctfile" to compile binary extensions to octave, I came across some curious behavior.

Executing the command:

g++-dp-4.0 -bundle -bundle_loader /opt/local/bin/octave-2.1.72 -Wl,-m -o ql_factorize.oct ql_factorize.o -L/opt/local/lib/octave-2.1.72 -loctinterp -loctave -lcruft -L/opt/local/lib -framework Accelerate -lfftw3 -lreadline -lncurses -lhdf5 -lz -lm -lgfortran

caused the following error (here shown verbatim):

g++-dp-4.0: couldn't run 'undle_loader-gcc-4.0.3': No such file or directory

Notice the missing "b" in "bundle".

Apparently, this is a known problem: see ​http://www.opendarwin.org/pipermail/cvs-darwinports-all/2005-February/058079.html

The fix is simple, at least as far as 'mkoctfile' is concerned. Simply add a "-v" as the first option, replacing the above command with:

g++-dp-4.0 -v -bundle -bundle_loader /opt/local/bin/octave-2.1.72 [...]

and the resultant compile/link works just fine.

This is a bug in gcc, obviously, but it also prevents the mkoctfile script from working within octave.

[markd@…]

Octave is now at 2.9.9 and gcc issues have been fixed. Any other or remaining problems should be opened on a new ticket.