#9519: scipy does not exit if there are build failures, but spkg-install looks
OK
------------------------+---------------------------------------------------
Reporter: drkirkby | Owner: GeorgSWeber
Type: defect | Status: new
Priority: major | Milestone: sage-4.5.1
Component: build | Keywords:
Author: | Upstream: None of the above - read trac for
reasoning.
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Comment(by drkirkby):
Replying to [comment:5 mpatel]:
> If enough parts of Sage run, you could try running the test suite, e.g.,
> {{{
> #!sh
> $ ./sage -sh
> sage subshell$ easy_install nose
> sage subshell$ exit
> $ ./sage -python -c "import scipy; scipy.test()"
> }}}
>
[http://sage.math.washington.edu/home/mpatel/trac/9519/scipy_nosetest.log
Here's the output] on sage.math with 4.5.
>
> I suppose we could optionally (if the user/developer desires) install
nose automatically.
I've never come across 'nose' - my python skills are next to zero. I will
attach a log. As you can see, it finally fails with a core dump, but
perhaps has some useful information before it dumps core.
BTW, I've removed the static atlas libs, leaving only the shared ones.
That might be a cause of a problem. I can't understand the need for both.
If yyou look in the ATLAS package, you can see about 3 dynamic libraries
will be missing. Two are not built, and one is deleted. I built them all
and deleted no dynamic ones - only the static.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9519#comment:7>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
