Jonathan Drews <[EMAIL PROTECTED]> writes: > > octave:1> 1 > > ans = 1 > > octave:2> 1+1 > > ans = 2 > > octave:3> quit > > tv@vador ~ $ rpm -q octave > > octave-2.1.36-3mdk > > That's great ! You are using the tarball form the Octave website?
by the time i updated octave, i used 3.2-0.3mdk. i didn't rebuild it with 3.2-1mdk but i don't expect it to break packages (1mdk has few changes on top of 0.3mdk). > Are you using beta 2 or beta 3? always current cooker, that is nearly beta3 > I will get the beta 3 CD's on Sunday and retest myself but I would > like to know if you compiled this from the tarball sources at > ftp://ftp.octave.org/pub/octave/bleeding-edge where do you want it to come else ? > If you did compile the octave-2.1.36 traball from here let me know > so I can write John Eaton back and tell him not to worry. i did. but note that i've applied a few patches on top of it. and note that previously to 2.1.36-3mdk, it was compiled with egcs. especially, octave-c-file-ptr-stream.patch.bz2 is there for newer c++ conformant compiler such as gcc-3.x this patch came from cvs
