On Mon, 30 Nov 2009 at 09:25PM -0800, Robert Bradshaw wrote:
Isn't there an option to set to run all the spkg internal tests?
Export SAGE_CHECK=yes before starting a build, which will run the spkg's
internal tests, as defined by the spkg-check script.
Last I knew, there were several spkgs which
Robert Bradshaw wrote:
Isn't there an option to set to run all the spkg internal tests?
- Robert
My point was, since MPFR seems to be pretty good at finding compiler bugs, it
was one worth running every time, whereas other tests may be less useful.
There is for example a bug in gcc 4.4.0
On Tue, 01 Dec 2009 at 09:51AM +, Dr. David Kirkby wrote:
My point was, since MPFR seems to be pretty good at finding compiler
bugs, it was one worth running every time, whereas other tests may be
less useful.
Checking the spkg-install file, I think they *are* run every time: at
the bottom
Dan Drake wrote:
On Tue, 01 Dec 2009 at 09:51AM +, Dr. David Kirkby wrote:
My point was, since MPFR seems to be pretty good at finding compiler
bugs, it was one worth running every time, whereas other tests may be
less useful.
Checking the spkg-install file, I think they *are* run every
Isn't there an option to set to run all the spkg internal tests?
- Robert
On Nov 29, 2009, at 2:16 AM, David Kirkby wrote:
I was just looking at
http://trac.sagemath.org/sage_trac/ticket/7095
os x 10.6 port -- numerous mysterious errors caused by weird 'abort
trap' issue
and see
I was just looking at
http://trac.sagemath.org/sage_trac/ticket/7095
os x 10.6 port -- numerous mysterious errors caused by weird 'abort
trap' issue
and see discussion about problems with different gcc versions.
I've noticed that the MPFR test suite seems to have a habbit of
picking up
