Re: [OctDev] Re: Octave 2.1.37 available for ftp

[Paul K. <pki...@rr...>]

On Wed, Oct 23, 2002 at 10:49:04PM +0100, Etienne Grossmann wrote:
> 
>   Hello,
> 
> I have just installed 2.1.37, but compilation of octave-forge ends
> with :
> 
> ======================================================================
> mkoctfile -DHAVE_OCTAVE_21 -v fsolve.cc
> g++ -c -fPIC -I/usr/local/include/octave-2.1.37 -I/usr/local/include/octave-2.1.37/octave -I/usr/local/include -mieee-fp -fno-implicit-templates -g -O2 -Wall -DHAVE_OCTAVE_21 fsolve.cc -o fsolve.o
> fsolve.cc: In function `class octave_value_list Ffsolve(const octave_value_list &, int)':
> fsolve.cc:211: no matching function for call to `NLEqn::set_options (NLEqn_options &)'
> make[1]: *** [fsolve.oct] Error 1
> make[1]: Leaving directory `/home/cdisk/etienne/prog/octave/octave-forge/octave-forge/FIXES'
> make: *** [FIXES/] Error 2
> ======================================================================
> 
>   I would like to check whether the backward compatibility problem
> with is_XXX() still exists, and if it does, transform all relevant
> sourceforge files.
> 
>   Since this is a big step, I guess the procedure is transform, test
> and send a patch for people to check, and then commit?

I say commit directly.  If anything really serious goes wrong we can
always back out.

Are we abandoning support for 2.1.36?

- Paul