[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugging .oct file building

From: Thomas Hoffmann
Subject: Re: Debugging .oct file building
Date: Fri, 15 Dec 2000 18:31:22 +0100 (MET)

> Sorry, that should be rebuild libstdc++ to be a shared library.  Isn't
> that the default now with gcc 2.95.x?  Did you build it from sources
> yourself?  Did you specifically request --disable-shared when you ran
> configure?

No. Just the opposite: install/CONFIGURE says

     * --enable-shared -- Build shared versions of the C++ runtime
       libraries if supported --disable-shared is the default.

So I forced the configuration into building shared libs. The compiling lead to a
struggle that did cost me the whole afternoon. Now that I have this shared lib,
I can run the mkoctfile unmodified and get an octfile which I can load, but that
crashes Octave:

-rw-rw-r--   1 hoffmann   users          438 Dec 14 11:25
-rw-rw-r--   1 hoffmann   users       101540 Dec 15 18:18 oregonator.o
-rwxrwxr-x   1 hoffmann   users       113704 Dec 15 18:21 oregonator.oct
bash-2.01$ octave
GNU Octave, version 2.0.14 (hppa1.1-hp-hpux10.20).
Copyright (C) 1996, 1997, 1998, 1999 John W. Eaton.
This is free software with ABSOLUTELY NO WARRANTY.
For details, type `warranty'.

octave:1> oregonator([1,2,3],0)
/usr/lib/ Unresolved symbol: elem__C17octave_value_listi (code)  from 
error: IOT instruction -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete

ABORT instruction (core dumped)

Do I need to rebuild Octave with shared libs now? 

Thomas Hoffmann.

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

Octave's home on the web:
How to fund new projects:
Subscription information:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]