release 3.2.1

[Sergei Steshenko]

--- On Wed, 7/15/09, John W. Eaton <jwe at octave.org> wrote:

> From: John W. Eaton <jwe at octave.org>
> Subject: Re: release 3.2.1
> To: "Sergei Steshenko" <sergstesh at yahoo.com>
> Cc: "Riccardo Corradini" <riccardocorradini at yahoo.it>, bug at octave.org
> Date: Wednesday, July 15, 2009, 7:09 PM
> On 15-Jul-2009, Sergei Steshenko
> wrote:
> 
> | 
> | 
> | --- On Wed, 7/15/09, John W. Eaton <jwe at octave.org>
> wrote:
> | 
> | > From: John W. Eaton <jwe at octave.org>
> | > Subject: Re: release 3.2.1
> | > To: "Riccardo Corradini" <riccardocorradini at yahoo.it>
> | > Cc: bug at octave.org
> | > Date: Wednesday, July 15, 2009, 11:33 AM
> | > On  7-Jul-2009, Riccardo
> | > Corradini wrote:
> | > 
> | 
> | [snip]
> | 
> | > I'm confused now.  Does this mean that you claim
> the
> | > bug is fixed,
> | > there is not really a bug, the bug is in ATLAS
> instead of
> | > Octave, or
> | > what?
> | > 
> | 
> | [snip]
> | 
> | It looks like the bug manifests itself with lapack-3.2
> rather than
> | lapack-3.1.1.
> | 
> | I have noticed similar behavior with octave-3.0.5, but I
> haven't had a chance to rebuild stUff again with various
> 'lapack' versions (3.1.1, 3.2)
> | and various 'atlas' versions (3.8.2, 3.8.3) in order to
> exactly tell which
> | version of what causes the bug to show up.
> | 
> | Though it looks like the bug is in 'lapack'/'atlas', it
> may also be that,
> | 
> | say, 'lapack' interface has changed, but 'octave' is
> unaware of this.
> 
> What about lapack 3.2.1?  Does that also show the
> problem for you?
> I'm using the Debian package for 3.2.1 and I don't see the
> problem.
> 
> jwe
> 

Yes - I actually meant lapack-3.2.1.

The point is that lapack-3.2* is significantly different from lapack-3.1*,
that's why it takes more than just to change version in my environment to
revert back to lapack-3.1.1.

Just to remind/clarify - I observe the problem in octave-3.0.5 - I am not
yet building octave-3.2*.

Regards,
  Sergei.