From octave-maintainers-request at bevo dot che dot wisc dot edu Wed Nov 20 21:43:01 2002 Subject: Re: Octave 2.1.40 available for ftp From: Dirk Eddelbuettel To: Paul Kienzle , octave-maintainers mailing list Date: Wed, 20 Nov 2002 21:42:58 -0600 Re-building octave-forge under Debian testing with 2.1.40 installed: mkoctfile -DHAVE_OCTAVE_21 -s -v conv2.cc /usr/bin/g++ -c -fPIC -I/usr/include/octave-2.1.40 -I/usr/include/octave-2.1.40/octave -I/usr/include -mieee-fp -fno-implicit-templates -O2 -DHAVE_OCTAVE_21 conv2.cc -o conv2.o conv2.cc: In function class MArray2 > conv2(MArray > &, MArray > &, MArray2 > &, int)': conv2.cc:271: instantiated from here conv2.cc:70: jump_to_top_level' undeclared (first use this function) conv2.cc:70: (Each undeclared identifier is reported only once conv2.cc:70: for each function it appears in.) make[3]: *** [conv2.oct] Error 1 make[3]: Leaving directory /home/edd/src/debian/octave-forge-2002.05.09/main/image' make[2]: *** [image/] Error 2 make[2]: Leaving directory /home/edd/src/debian/octave-forge-2002.05.09/main' make[1]: *** [main/] Error 2 make[1]: Leaving directory /home/edd/src/debian/octave-forge-2002.05.09' make: *** [build-stamp] Error 2 Any ideas? Dirk On Wed, Nov 20, 2002 at 04:10:20PM -0500, Paul Kienzle wrote: > I had to add #include to the top of libcruft/misc/quit.h > in order to get DASPK.cc to compile (using 2.1.40 from CVS). > > Paul > > On Wed, Nov 20, 2002 at 01:38:18PM -0600, John W. Eaton wrote: > > Octave 2.1.40 is now available for ftp from ftp.octave.org in the > > directory /pub/octave/bleeding-edge: > > > > -rw-r--r-- ftpadm ftp 4892619 Nov 20 13:25 octave-2.1.40.tar.gz > > -rw-r--r-- ftpadm ftp 3825982 Nov 20 13:25 octave-2.1.40.tar.bz2 > > -rw-r--r-- ftpadm ftp 80465 Nov 20 13:27 octave-2.1.39-2.1.40.patch.gz > > -rw-r--r-- ftpadm ftp 67290 Nov 20 13:27 octave-2.1.39-2.1.40.patch.bz2 > > > > This version uses C++ exception handling for cleaning up after > > interrupt signals (Control-C). Please report any problems you notice, > > such as Octave not responding in a reasonable amount of time to an > > interrupt. > > > > If your favorite bug is still not fixed, please let me know about it. > > > > Thanks, > > > > jwe > > > > -- > > www.octave.org | Unfortunately we were hopelessly optimistic in 1954 > > www.che.wisc.edu/~jwe | about the problems of debugging FORTRAN programs. > > | -- J. Backus > > > -- Prediction is very difficult, especially about the future. -- Niels Bohr