[SciPy-dev] scipy on irix -- problems with bsplines

[eric jones]

> -----Original Message-----
> From: scipy-dev-admin at scipy.net [mailto:scipy-dev-admin at scipy.net] On
> Behalf Of Pearu Peterson
> Sent: Thursday, July 04, 2002 4:12 AM
> To: scipy-dev at scipy.net
> Subject: RE: [SciPy-dev] scipy on irix -- problems with bsplines
> 
> 
> On Mon, 1 Jul 2002, eric jones wrote:
> 
> >
> > I hadn't, but I just tried this, and it still dies at:
> >
> > Reading fortran codes...
> >         Reading file
> >
'/home/army/eric/third/sgi_cc/SciPy-0.2.0_alpha_103.3566/linalg/flapack.
> > pyf'
> > Post-processing...
> >         Block: cgees__user__routines
> >                 Block: cgees_user_interface
> >                         Block: cselect
> >         Block: dgees__user__routines
> >                 Block: dgees_user_interface
> >                         Block: dselect
> >         Block: sgees__user__routines
> >                 Block: sgees_user_interface
> >                         Block: sselect
> >         Block: zgees__user__routines
> >                 Block: zgees_user_interface
> >                         Block: zselect
> >         Block: flapack
> >                         Block: sgesv
> >                         Block: dgesv
> >                         Block: cgesv
> >                         Block: zgesv
> >                         Block: sgetrf
> >                         Block: dgetrf
> >                         Block: cgetrf
> >                         Block: zgetrf
> >                         Block: sgetrs
> >                         Block: dgetrs
> >                         Block: cgetrs
> >                         Block: zgetrs
> >                         Block: sgetri
> >                         Block: dgetri
> >                         Block: cgetri
> >                         Block: zgetri
> >                         Block: sgesdd
> > Bus error (core dumped)
> 
> That is strange. Note that f2py2e is a pure Python package and
therefore I
> would not expect any core dumps from using f2py unless Python itself
has
> bugs or there are problems with Python builds.

Right.  I agree.  That is what I suspected also.  I haven't had time to
chase this one further though.  The only things slightly unusual about
the build are that I built and linked readline and ncurses myself
because the system doesn't have those.  These were build with gcc.  The
Python build was built with MIPSPro.  I wouldn't have thought
readline/ncurses would cause this sort of problem.

eric