mkoctfile and mex broken on Mac 10.6 Snow Leopard (with patch of a sort)

[RickG]

Using octave-3.2.3-i386.dmg mex and mkoctfile got lots of errors caused by
architecture mismatches.
This is because GCC is defaulting to x86_64 but Octave is built as i386.

patch for the time being is to put

CFLAGS=”-arch i386 ${CFLAGS}”
FFLAGS=”-arch i386 ${FFLAGS}”
CPPFLAGS=”-arch i386 ${CPPFLAGS}”
CXXFLAGS=”-arch i386 ${CXXFLAGS}”
LDFLAGS=”-arch i386 ${LDFLAGS}”

just after

set -e

in mkoctfile-3.2.3 (or whatever version) in
/Applications/Octave.app/Contents/Resources/bin/

(it probably really belongs in mkoctfile-orig or something like that so it
winds up in the right place
during the build process)

(TapeDeck 1.2 on SuperMegaUltraGroovy had the basic idea for this fix, but
he put it directlly
in ..bin/mkoctfile,  where it doesn't get executed if you do mex or
mkoctfile from within Octave)


-- 
View this message in context: 
http://www.nabble.com/mkoctfile-and-mex-broken-on-Mac-10.6-Snow-Leopard-%28with-patch-of-a-sort%29-tp25895204p25895204.html
Sent from the Octave - General mailing list archive at Nabble.com.