help-octave
[Top][All Lists]
Advanced

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

Re: fatal errors running octave 2.09 under Irix6.2 (in libcruft.so?)


From: John W. Eaton
Subject: Re: fatal errors running octave 2.09 under Irix6.2 (in libcruft.so?)
Date: Thu, 21 Aug 1997 06:47:09 -0500

On 21-Aug-1997, Jonathan King <address@hidden> wrote:

| This might be relevant:  The package I grabbed off of netlib claimed
| to build the whole libf2c in one fell swoop rather than libI77 and
| libF77. But it did seem to build a libf2c.a (not a libf2c.so) and
| put it where it was supposed to in /usr/freeware/lib.  However...

It's probably ok that libf2c is not a shared library.

| >What was the output
| >from running configure on your system?
| 
| I must really be losing it.  There was reams and reams of
| config.log, and a bunch of other config.* files, but the only place I
| could really find the "results" of confis was in the text of
| octave-bug. Is this correct?

I meant the output that is printed to the screen, for starters.

| And then reams of symbols.  But I presume it's a very bad sign that
| libf2c doesn't show up *anywhere* here; where should it have been?

It should be in FLIBS.  You can either fix your installation so
that configure can find libf2c, then rerun configure, or you can edit
Makeconf and define FLIBS to be -lf2c or /dir/where/libf2c/lives/libf2c.a.

| I guess I do find it weird that configure didn't spit out an 
| obvious message like "Can't build octave without some kind of
| usable fortran set-up, so don't even try."

If Octave's configure script fails to find a compatible fortran
compiler or f2c, it prints:

  configure: warning: in order to build octave, you must have a compatible
  configure: warning: Fortran compiler or f2c installed and in your path.
  configure: error: See the file INSTALL for more information.

If it finds f2c but fails to find libf2c, it prints:

  configure: warning: I found f2c but not libf2c.a, or libF77.a and libI77.a

I realize that these messages are somewhat buried in the list of all
the others.  I'll consider making these problems fatal and adding a
--with-f77libs=ARG option to allow overriding the default.

Thanks,

jwe



reply via email to

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