octave 1.1 on SunOS 4.1.3

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

octave 1.1 on SunOS 4.1.3

Vinayak Dutt
Hi Octave users:

 I had written earlier about the problems of compiling octave 1.1
on SunOS 4.1.3 with gcc-2.6.0 and Sun F77 2.0.1.

 I thought I had fixed compile problems by adding
/usr/lang/SC2.0.1/values-Xs.o (/usr/lang is the directory where
SparcCompilers are installed). It removed the undefined __lib_version
symbol problem. But now I get problems with loading some library
functions when octave is run. For example, when I run function
image() in octave, I get following error message:

octave:1> image()
error: failed to link library /usr/lang/SC2.0.1/values-Xs.o
error: unable to load builtin function rand
error: evaluating expression near line 45, column 32
error: evaluating binary operator `*' near line 45, column 32
error: evaluating argument list element number 0
error: evaluating index expression near line 45, column 26
error: evaluating argument list element number 0
error: evaluating index expression near line 45, column 21
error: evaluating assignment expression near line 45, column 11
error: called from `image' in file `/home/us0/vdp/local/octave/lib/octave/1.1.0/m/image/image.m'
octave:2>

 So the fix is causing some other problems. I appears to me that
the link editor job to finally obtain the octave binary from the
objects should be done by the Fortran compiler rather than c++ compiler.
But I have no idea how to modify the configuration script to achieve
that. If any other user has a fix for this SunOS problem, then please
post it to this mailing list.

Thanks


--vinayak-
/*
 * vinayak dutt
 * graduate student, ultrasound research
 * mayo graduate school, rochester mn
 *
 * e-mail: [hidden email]
 *         [hidden email]
 *
 */
#include "disclaimer.h"

Reply | Threaded
Open this post in threaded view
|

Re: octave 1.1 on SunOS 4.1.3

niles-5

: I had written earlier about the problems of compiling octave 1.1
:on SunOS 4.1.3 with gcc-2.6.0 and Sun F77 2.0.1.

**********************************************************
*                                                        *
*  To compile Octave, you will need a recent version of  *
*  GNU Make.                                             *
*                                                        *
*  You will also need g++ version 2.6.3 or later, and    *
*  libg++ version 2.6.1 or later.                        *
*                                                        *
*  Now would be a good time to read INSTALL.OCTAVE if    *
*  you have not done so already.                         *
*                                                        *
**********************************************************


In other words, you NEED TO UPDATE your gcc to 2.6.3!!!

        Give it a try,

                Rick Niles.

Reply | Threaded
Open this post in threaded view
|

Re: octave 1.1 on SunOS 4.1.3

Vinayak Dutt
In reply to this post by Vinayak Dutt
#
#: I had written earlier about the problems of compiling octave 1.1
#:on SunOS 4.1.3 with gcc-2.6.0 and Sun F77 2.0.1.
#
#**********************************************************
#*                                                        *
#*  To compile Octave, you will need a recent version of  *
#*  GNU Make.                                             *
#*                                                        *
#*  You will also need g++ version 2.6.3 or later, and    *
#*  libg++ version 2.6.1 or later.                        *
#*                                                        *
#*  Now would be a good time to read INSTALL.OCTAVE if    *
#*  you have not done so already.                         *
#*                                                        *
#**********************************************************
#
#
#In other words, you NEED TO UPDATE your gcc to 2.6.3!!!
#

  Yes. I noticed that yesterday when I looked into the details. But
I had noticed earlier somewhere else in the docs that one needs 2.6.0
and up, so I thought I will give it a try with 2.6.0. Anyway, I will
try to upgrade gcc as soon as possible. But as I mentioned in my blurb,
the problem does not seem much to do with gcc, but link editing. I was
getting missing symbol (__lib_version) which I think is used by
Sun compiler. So it is much to do with what all objects have to be linked
to resolve all the symbols rather that which compiler I chose.

  By the way, yesterday night I was able to install octave with
gcc-2.6.0 and Sun F77-2.0.1 with my fix of including Sun compiler
object version-Xs.o from the library directory of Sun compiler.
Only problem was that I could not used dld library and lite-kernel option.
So now I have a 3mb+ binary :-( But octave seems to be working fine.


--vinayak-
/*
 * vinayak dutt
 * graduate student, ultrasound research
 * mayo graduate school, rochester mn
 *
 * e-mail: [hidden email]
 *         [hidden email]
 *
 */
#include "disclaimer.h"

Reply | Threaded
Open this post in threaded view
|

Re: octave 1.1 on SunOS 4.1.3

Vinayak Dutt
In reply to this post by Vinayak Dutt
[hidden email] replies:
#[hidden email] (Vinayak Dutt) wrote:
#
#:  I had written earlier about the problems of compiling octave 1.1
#: on SunOS 4.1.3 with gcc-2.6.0 and Sun F77 2.0.1.
#:
#:  I thought I had fixed compile problems by adding
#: /usr/lang/SC2.0.1/values-Xs.o (/usr/lang is the directory where
#: SparcCompilers are installed). It removed the undefined __lib_version
#: symbol problem. But now I get problems with loading some library
#: functions when octave is run. For example, when I run function
#: image() in octave, I get following error message:
#:
#: octave:1> image()
#: error: failed to link library /usr/lang/SC2.0.1/values-Xs.o
#
#The fix of adding values-Xs.o to FLIBS may be ok, but then we also
#need to remove any .o files from FLIB_LIST in Makeconf.
#

values-Xs.o is the only .o file in FLIB_LIST :-(

i think gnu dld might have problems working with sparc objects generated
by sparc compilers ???

i can't figure out what exactly could be ther problem. so temporarily
i have compiled octave without dld (so my binary is something like
5mb+ in size), but i have working octave, which matters more to me
as i have got my phd thesis work to finish :^0

our lab is in transition situation, migrating to
solaris 2.4 finally. so i would rather wait till that os upgrade and
work on compiling octave for solaris and look into gnu dld problem
with solaris. i suppose that problem would exist for solaris also :-(


--vinayak-
/*
 * vinayak dutt
 * graduate student, ultrasound research
 * mayo graduate school, rochester mn
 *
 * e-mail: [hidden email]
 *         [hidden email]
 *
 */
#include "disclaimer.h"