From bug-octave-request at bevo dot che dot wisc dot edu  Wed Dec 10 14:03:08 1997
Subject: immediate coredump on RH5.0 alpha
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: speier at sugar-land dot spc dot slb dot com
Cc: bug-octave at bevo dot che dot wisc dot edu
Date: Wed, 10 Dec 1997 14:04:57 -0600

On 10-Dec-2017, speier at sugar-land dot spc dot slb dot com <speier@sugar-land.spc.slb.com> wrote:

| Now Octave dumps core directly after startup, even after erasing the 
| -lgcc and -lc flags from the CXXLIBS definition.

| I mainly use the octave libraries. Linking programs (that worked on a 
| SuSE441 PC) against the octave libraries with including -lc and lgcc results 
| in immediated coredumps. Without including -lc and lgcc I get the following
| messages:
| 
| g++ -o my_prog.o -static -g -Wall  -L/usr/local/lib -loctave -L/usr/local/lib -lcruft -lf2c -lm 
| /usr/lib/libc.a(iofclose.o): In function `_IO_fclose':
| /usr/src/bs/BUILD/glibc-2.0.5/libio/iofclose.c:33: multiple definition of `_IO_fclose'
| /usr/lib/libstdc++.a(iofclose.o):/usr/src/bs/BUILD/libg++-2.7.2/libio/iofclose.c:33: first defined here
| ld: Warning: size of symbol `_IO_fclose' changed from 192 to 396 in iofclose.o
| /usr/lib/libc.a(iofflush.o): In function `_IO_fflush':
| /usr/src/bs/BUILD/glibc-2.0.5/libio/iofflush.c:31: multiple definition of `_IO_fflush'
| /usr/lib/libstdc++.a(iofflush.o):/usr/src/bs/BUILD/libg++-2.7.2/libio/iofflush.c:30: first defined here
| ....
| 
| So it seems that there is still a conflict between libstdc++ and libg++. 

Any libio stuff used in libg++ and libstdc++ should be compatible if
your libraries are properly installed.

As a quick workaround, try linking with c++ instead of g++ -- then the
-lg++ flag should not be passed to the linker (use -v to make sure it
is not).  I don't think Octave requires any functions from libg++ now,
so I would expect this to work unless you use some functions from
libg++ in your own code.

| P.S. the OSF4.0 binary works well, except that it does not find(?) xv. 
| Can this be configured? Unfortunately, I need the libraries, so running 
| the binary does not help me too much.

Is xv somewhere in your PATH?  The only place I know of that Octave
calls xv is image.m, using a shell command.  If xv is in your path,
Octave should use it.

jwe