Compiling Octave for MacOS X

[John W. Eaton]

On 28-Nov-2000, Harald Binder <address@hidden> wrote:

| I'm still (see my last message) trying to compile Octave for MacOS X.
| I got pretty far (I think all the librarys compile) up to this point
| ...
| make[3]: Nothing to be done for `all'.
| echo making all in liboctave
| making all in liboctave
| cd liboctave ; make all
| c++ -c  -I. -I.. -I../liboctave -I../src -I../libcruft/misc  -I../glob 
-I../glob -DHAVE_CONFIG_H -fno-rtti -fno-exceptions -fno-implicit-templates -g 
-O2 -Wall Array-C.cc
| Array2-idx.h: In function `int assign<Complex, 
Complex>(Array2<complex<double> > &, const Array2<complex<double> > &)':
| Array-C.cc:47:   instantiated from here
| Array2-idx.h:694: Internal compiler error.
| Array2-idx.h:694: Please submit a full bug report via the
| Array2-idx.h:694: <URL:http://developer.apple.com/bugreporter> web page.
| make[2]: *** [Array-C.o] Error 1
| make[1]: *** [liboctave] Error 2
| make: *** [all] Error 2

This is definitely a compiler bug.  A reliable compiler should never
crash (at least that's what I remember reading in the Bugs chapter of
the GCC manual).

| or sometimes:

Only sometimes, or always, when you try to compile this file?

| c++ -c  -I. -I.. -I../liboctave -I../src -I../libcruft/misc  -I../glob 
-I../glob -DHAVE_CONFIG_H -fno-rtti -fno-exceptions -fno-implicit-templates -g 
-O2 -Wall Array-C.cc
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L50$pb"} @ file 
address 43720.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L50$pb"} @ file 
address 43716.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L50$pb"} @ file 
address 43712.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L50$pb"} @ file 
address 43676.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L50$pb"} @ file 
address 43664.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L45$pb"} @ file 
address 42536.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L45$pb"} @ file 
address 42532.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L45$pb"} @ file 
address 42468.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L45$pb"} @ file 
address 42464.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L44$pb"} @ file 
address 42268.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L44$pb"} @ file 
address 42264.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L43$pb"} @ file 
address 41960.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L43$pb"} @ file 
address 41956.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L27$pb"} @ file 
address 13264.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L27$pb"} @ file 
address 13260.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L27$pb"} @ file 
address 13224.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L27$pb"} @ file 
address 13220.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L24$pb"} @ file 
address 12756.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L24$pb"} @ file 
address 12752.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L24$pb"} @ file 
address 12716.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L24$pb"} @ file 
address 12712.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L9$pb"} @ file 
address 772.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L9$pb"} @ file 
address 768.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L9$pb"} @ file 
address 732.
| /var/tmp/cc003602.s:unknown:Can't emit reloc {- symbol "L9$pb"} @ file 
address 728.
| make[2]: *** [Array-C.o] Error 1
| make[1]: *** [liboctave] Error 2
| make: *** [all] Error 2

This also looks like a compiler (or assembler?) bug to me.

| Does anybody know what could be the reason that the compiler gets such 
confused? Is there a workaround? Would there exist the possibility to 
cross-compile the code on an other machine?
| I must confess, that I am no C++ programmer...
| 
| By the way: The cc compiler identifies itself this way:
| root# cc -v
| Reading specs from /usr/libexec/ppc/2.95.2/specs
| Apple Computer, Inc. version cc-796.3, based on gcc driver version 2.7.2.1 
executing gcc version 2.95.2
| 
| Can anybody help me?
| That would be really very nice because it is rather frustrating to be stuck 
so near (I believe) to the successful build :-(

What version of Octave are you using?  What other tools?

jwe



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

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