Re: On entry to DLASDA parameter number 2 had an illegal value

[lo]

On Monday 26 July 2010 00:34:54 Dmitri A. Sergatskov wrote:
> On Sun, Jul 25, 2010 at 4:14 PM, lo <address@hidden> wrote:
> > hello,
> >
> > on running the following under octave 3.3.51 on a Linux Suse 11.2
> >
> > A = [ 0.50374   0.61402   0.43301; 0.60290   0.78609   0.43301 ]
> > B = [ -1.0531; -1.0531 ]
> > X = A\B; % solve A X = B
> >
> >
> > I get:
> >
> >  ** On entry to DLASDA parameter number  2 had an illegal value
> > A =
> >
> >   0.50374   0.61402   0.43301
> >   0.60290   0.78609   0.43301
> >
> > B =
> >
> >  -1.0531
> >  -1.0531
> >
> > error: test: exception encountered in Fortran subroutine dgelsd_
> >
> >
> > thanks for any help,
> >
> > regards,
> > Laurent
> 
> It works for me on Fedora 12 x86_64 with octave 3.3.51.
> I suspect that your lapack library is bad.
> Did you compile octave yourself?
> Did it pass all checks? (Did you "make check" in the build directory?)
> 
> Sincerely,
> 
> Dmitri.
> --
> 

I compiled octave myself;
lapack is provided by SuSE;
I downloaded the latest lapack version, 3.2.2, compiled and installed it;
running make check, I observe that this error message is also issued for some 
tests, for instance:

  scripts/optimization/fsolve.m .......................... ** On entry to 
DLASDA parameter number  2 had an illegal value
 ** On entry to DLASDA parameter number  2 had an illegal value                 
                                         
 PASS    4/6    FAIL 2                                                          
                                         
  scripts/optimization/fzero.m ........................... PASS    2/2          
                                         
  scripts/optimization/lsqnonneg.m ....................... PASS    2/2          
                                         
  scripts/optimization/optimset.m ........................ PASS    2/2          
                                         
  scripts/optimization/pqpnonneg.m ....................... ** On entry to 
DLASDA parameter number  2 had an illegal value

according to Jaroslav, ARPACK might pose problem;
I will have a look at it;

regards,
Laurent