From help-octave-request at bevo dot che dot wisc dot edu  Mon Jan 31 04:29:08 2000
Subject: compile on Cray/ nonGNUcompiler
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: Daniel Heiserer <Daniel dot Heiserer at bmw dot de>
Cc: "help-octave at bevo dot che dot wisc dot edu" <help-octave@bevo.che.wisc.edu>
Date: Mon, 31 Jan 2000 04:28:55 -0600 (CST)

On 31-Jan-2000, Daniel Heiserer <Daniel dot Heiserer at bmw dot de> wrote:

| did ever anybody successfully compile 
| octave on a Cray-SV1?
| 
| Or did ever anybody compile octave on SGI without the
| gnu-C Compiler?
| 
| Or has anybody that much insight into the code,
| that he (or she?) knows how big the effort is to change
| the octave code to be compileable with ANY 
| ANSI C++ Compiler?

It would require some work to accomodate compilers that are strict
about namespaces.

There are also some features of the GNU iostream implementation that
are used (the scan member function for istreams comes to mind).

I don't think these are impossible (or even terribly difficult)
problems to solve, but I've never needed to solve them, and so far, no
one has posted bug reports about them, so I guess it is not much of a
concern for most Octave users.

One way to help make Octave work with compilers other than g++, is to
try compiling it with another compiler and then report problems as you
find them.

Thanks,

jwe



-----------------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.che.wisc.edu/octave/octave.html
How to fund new projects:  http://www.che.wisc.edu/octave/funding.html
Subscription information:  http://www.che.wisc.edu/octave/archive.html
-----------------------------------------------------------------------