Ask Your Question
1

Install on 32bit fedora 12

asked 14 years ago

outway gravatar image

updated 14 years ago

Evgeny gravatar image

I've downloaded the sage source and proceeded according to README.txt (export SAGE_CHECK="yes"; make). Something with the python stuff went wrong, see below:

# tail -50 install.log 
test_zipfile
test_zipfile64
test_zipfile64 skipped -- test requires loads of disk-space bytes and a long time to run
test_zipimport
test_zipimport_support
test_zlib
test test_zlib failed -- Traceback (most recent call last):
  File "/usr/local/bin/sage-4.5.3/spkg/build/python-2.6.4.p9/src/Lib/test/test_zlib.py", line 84, in test_baddecompressobj
    self.assertRaises(ValueError, zlib.decompressobj, 0)
AssertionError: ValueError not raised

325 tests OK.
4 tests failed:
    test_commands test_distutils test_httpservers test_zlib
36 tests skipped:
    test_aepack test_al test_applesingle test_bsddb test_bsddb185
    test_bsddb3 test_cd test_cl test_codecmaps_cn test_codecmaps_hk
    test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw test_curses
    test_gl test_imgfile test_kqueue test_linuxaudiodev test_macos
    test_macostools test_normalization test_ossaudiodev test_pep277
    test_py3kwarn test_scriptpackages test_smtpnet test_socketserver
    test_ssl test_startfile test_sunaudiodev test_timeout
    test_urllib2net test_urllibnet test_winreg test_winsound
    test_zipfile64
2 skips unexpected on linux2:
    test_ssl test_bsddb
make[2]: *** [test] Error 1
make[2]: Leaving directory `/usr/local/bin/sage-4.5.3/spkg/build/python-2.6.4.p9/src'
An error occurred while testing Python
*************************************
Error testing package ** python-2.6.4.p9 **
*************************************
sage: An error occurred while testing python-2.6.4.p9
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /usr/local/bin/sage-4.5.3/install.log.  Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/usr/local/bin/sage-4.5.3/spkg/build/python-2.6.4.p9 and type 'make check' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
(cd '/usr/local/bin/sage-4.5.3/spkg/build/python-2.6.4.p9' && '/usr/local/bin/sage-4.5.3/sage' -sh)
When you are done debugging, you can type "exit" to leave the
subshell.
make[1]: *** [installed/python-2.6.4.p9] Error 1
make[1]: Leaving directory `/usr/local/bin/sage-4.5.3/spkg'

real    16m38.117s
user    8m34.452s
sys 2m27.841s
Error building Sage.
Preview: (hide)

Comments

if you could edit this post, wrapping the log output in '<pre>' and '</pre>', it would be easier to read :)

niles gravatar imageniles ( 14 years ago )

or easier - select the text that should be pre-formatted and hit the "format code" button - the one that has digits on it.

Evgeny gravatar imageEvgeny ( 14 years ago )

thanks, will do so next time.

outway gravatar imageoutway ( 14 years ago )

1 Answer

Sort by » oldest newest most voted
2

answered 14 years ago

I don't know of a single system on which python passes its self-check. I would suggest unsetting SAGE_CHECK and trying "make" again. (Or unset SAGE_CHECK and install just the python package by typing "./sage -i spkg/standard/python-2.6.4.p9.spkg". Once that's done, you can do "export SAGE_CHECK=yes; make" again to build the rest of Sage.)

Preview: (hide)
link

Comments

thank you, reinstalling without SAGE_CHECK set worked. Interestingly it took ~6 times longer. Any explanation for that? How can I run the checks now after the build, if possible without make?

outway gravatar imageoutway ( 14 years ago )

When you install Sage, it builds roughly 100 packages. When one of them fails, as python did with SAGE_CHECK=yes, then the process stops, possibly with only a small fraction of the packages completed. If the process succeeds, all of them build, so it will take longer, possibly a lot longer.

John Palmieri gravatar imageJohn Palmieri ( 14 years ago )

As far as testing, I don't know how to test each package after the build, but you can run "sage -testall" to run Sage's test suite.

John Palmieri gravatar imageJohn Palmieri ( 14 years ago )

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 14 years ago

Seen: 734 times

Last updated: Sep 12 '10