Re: Building Octave Statically (and without graphics)

[John W. Eaton]

On  6-Mar-2009, Jason Riedy wrote:

| And John W. Eaton writes:
| > Building static binaries isn't normal usage these days, so it is not
| > surprising to me that some things don't work correctly.
| 
| Alas, it is expected usage for certain clusters and parallel
| machines.  There is a page detailing how people built an older
| Octave for BG/L that *may* be of use to the original poster:
|   
http://www.pdc.kth.se/resources/computers/bluegene/bgloctave/mpitb-octave-on-bgl
| 
| There would be much (some?) rejoicing if someone would tackle a
| --build-static-octave configure option...

If you build Octave this way, is it OK to completely disable the
ability to use .oct and .mex functions?  Or do you want some (easy)
way to be able to do something like put a bunch of .cc files (that
would normally be used to build a set of .oct files) in a directory
and have them built as part of Octave?  I think that might be
possible, but would require more work for mex files since they all
use the same function name (mexFunction).

jwe