From octave-maintainers-request at bevo dot che dot wisc dot edu Fri Jul 27 03:40:01 2001
Subject: Linking problems in alpha
From: Teemu Ikonen <tpikonen at pcu dot helsinki dot fi>
To: octave-maintainers at bevo dot che dot wisc dot edu, help-octave@bevo.che.wisc.edu
Date: Fri, 27 Jul 2001 11:39:49 +0300

Hi everybody,

I was trying to compile Octave-2.1.34 in OSF1 V4.0 878 alpha -system.
Compilation goes fine, but the final linking step doesn't. I get the
following error message:

----------------

make[2]: Entering directory /scratch/tpikonen/octave-2.1.34/src'
c++  -I. -I.. -I../liboctave -I../src -I../libcruft/misc  -I../glob
-I../glob -DHAVE_CONFIG_H -mieee-with-inexact -fno-implicit-templates -g -O2
-Wall -rdynamic \
-L..    -g -o octave \
octave.o builtins.o ops.o ../libcruft/blas-xtra/xerbla.o  balance.o
besselj.o  betainc.o  chol.o  colloc.o  dassl.o  det.o  eig.o  expm.o  fft.o
fft2.o  filter.o  find.o  fsolve.o  gammainc.o  getgrent.o  getpwent.o
getrusage.o  givens.o  hess.o  ifft.o  ifft2.o  inv.o  log.o  lpsolve.o
lsode.o  lu.o  minmax.o  pinv.o  qr.o  quad.o  qz.o  rand.o  schur.o  sort.o
svd.o  syl.o  time.o \
-L../liboctave -L../libcruft -L../src -Xlinker -rpath -Xlinker
/usr/local/contrib/gnu/lib/octave-2.1.34 \
../src/liboctinterp.a ../liboctave/liboctave.a  ../libcruft/libcruft.a
../readline/libreadline.a ../kpathsea/libkpathsea.a ../glob/glob.o
../glob/fnmatch.o  \
 -lncurses -ldxml -lz -lm  -lg2c -lm
-L/usr/local/lib/gcc-lib/alphaev5-dec-osf4.0d/2.95.1 -L/usr/lib/cmplrs/cc
-L/usr/local/lib -lm
c++: unrecognized option -rdynamic'
/usr/bin/ld:
write_obj: malloc(215104.) failed
collect2: ld returned 1 exit status
make[2]: *** [octave] Error 1
make[2]: Leaving directory /scratch/tpikonen/octave-2.1.34/src'
make[1]: *** [src] Error 2
make[1]: Leaving directory /scratch/tpikonen/octave-2.1.34'
make: *** [all] Error 2

-----------------

The size of the ld -process grows to about 200M during linking, which
shouldn't be over any memory limits I have. I also tried linking with 
GNU ld, but that resulted in another set of error messages. The version of
gcc I used was 2.95.1.

I've successfully compiled Octave 2.1.31 on the same system, so the breakage
of this version is a bit of a mystery. If someone has experience on compiling
the latest Octave on alpha, I'd appreciate if you could help me.

Teemu