On 04/30/11 09:59 PM, Alex Lara wrote:
The command ./sage -f python (after install libssl-dev) did not work,
but sage -f python-2.6.4.p10.spkg did work (I think).
I ran make test. The following test failed:
sage -t -force_lib "devel/sage/sage/rings/number_field/
number_field.py"
Do you think my build is ok now?
Best regards---Alex
In a word, No. What version of Sage are you trying to build?
Can you show us the output of the test log file (test.log, ptest.log,
ptestlong.log or whatever it is in your case). We need to see the bit where the
test fails - not the complete log.
If you have not run the long tests, I suggest you run them too.
$ make testlong
(run each test serially)
or
$ make ptestlong
(if you have a multi-core and/or multi-processor machine, which will run tests
in parallel to reduce the time needed to run them).
I have a faint recollection of "number_field.py" might have failed on one of the
recent alpha releases, but has been fixed. Depending on what you are using, you
might have hit a problem that's been solved. But I could be mistaken about this
anyway - I lose track of the test failures, which are quite common in the early
alpha releases.
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
