From octave-maintainers-request at bevo dot che dot wisc dot edu  Tue Feb  8 01:08:10 2000
Subject: Octave 2.1.26 available for ftp
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: octave-maintainers at bevo dot che dot wisc dot edu
Date: Tue, 8 Feb 2000 01:09:14 -0600

Octave 2.1.26 is now available for ftp from ftp.che.wisc.edu in the
directory /pub/octave/bleeding-edge along with a patch from the
previous version:

  -rw-r--r--   1 jwe  3803427 Feb  8 00:10 octave-2.1.26.tar.bz2
  -rw-r--r--   1 jwe  4761486 Feb  8 00:10 octave-2.1.26.tar.gz
  -rw-r--r--   1 jwe   156511 Feb  8 00:49 octave-2.1.25-2.1.26.patch.bz2
  -rw-r--r--   1 jwe   196980 Feb  8 00:49 octave-2.1.25-2.1.26.patch.gz

Some notes:

  * To generate the manual and other documentation now requires the
    tools distributed with texinfo-4.0.

  * You probably need gcc-2.95.x to build the C++ parts of Octave now.

If you want to attempt to compile this with some compiler other than
g++, you can do something like this:

  1. Tell configure what compilers to use.  There are probably other
     ways, but here is one that will work to set the C compiler to
     `cc', the C++ compiler to `CC', and the Fortran compiler to
     `f77'):

       CC=cc CXX=CC ./configure --with-f77

  2. (Maybe) fix the rules for generating .d files in the generated
     Makeconf file (or Makeconf.in, if you want the change to persist
     for more than one configure or config.status run).  For the Sun
     compilers that I used, the only change that was needed was to
     change the -M flag to be -xM instead.

  3. Run make.

  4. Fix any problems that show up.  Whether or not you can fix the
     problems, please do report them.

Don't expect everything it to get as far as linking, but it is much
closer to working than it used to be.

Thanks,

jwe