[Octave-bug-tracker] [bug #34169] Support -f compiler flags in mkoctfile

[Jordi Gutiérrez Hermoso]

Follow-up Comment #1, bug #34169 (project octave):

I think this is the wrong fix. There are many other useful flags we could pass
to the compiler, and manually adding each to mkoctfile seems laborious.
Rather, it should probably simply pass any unrecognised flags to the
compilation command, and we should only make mkoctfile itself accept long
options as to reduce the likelihood of clashing with one of the compiler's
short options (maybe even prefix them, e.g. --mko-mex, --mko-print).

Note that there is also src/mkoctfile.cc.in for the benefit of our
POSIX-hating Windows friends which this patch ignores. Also see this thread:

http://octave.1599824.n4.nabble.com/I-think-I-quot-broke-quot-mkoctfile-for-3-4-1-td3608378.html

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?34169>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/