From maintainers-request at octave dot org Tue Mar 21 10:00:50 2006
Subject: Re: octave on biowulf
From: "Tom Holroyd (NIH/NIMH) [E]" <tomh at kurage dot nimh dot nih dot gov>
To: Jason Russler <jrussler at helix dot nih dot gov>
CC: Susan Chacko <susanc at helix dot nih dot gov>, maintainers@octave.org
Date: Tue, 21 Mar 2006 10:54:48 -0500

Hi, Jason.

Hmm.  The Octave on Biowulf is 2.9.4, but it doesn't appear to be the latest version.  Perhaps that has been the source of some of the trouble.  The latest CVS of Octave shows up as 2.9.4, but is copyright 2006, while the one on Biowulf is 2005.  (The octave maintainers have not bumped the version number since the 2.9.4 release on 11 Nov 2005, despite massive internal changes---perhaps they really should have.)  Only the recent CVS will work.

For example, on biowulf, using the 11 Nov 2005 release (labeled 2.9.4),

octave:1> all([0 1])
error: T& Array<T>::checkelem (2): range error

while on my machine, with the most recent version (also called 2.9.4, sadly),

octave:1> all([0 1])
ans = 0

needless to say, this is a very basic array operation and octave is more-or-less useless with bugs of this sort.

Sorry for the confusion about the versions.

Thanks,
Tom