I copied a complete file system containing my home directory (and so a
build of Sage) from one machine to another. I then run all the doc
tests. One test failed on the new machine, despite all tests passing
on the original machine.
The following tests failed:
sage -t -force_lib "devel/sage/sage/misc/preparser.py"
Total time for all tests: 10776.5 seconds
When I look at the test failure, it appears that the test tried to
compile a file, which would not work, as the system had no gcc or
other compiler.
drkir...@laptop:~/sage-4.6.1.alpha2$ ./sage -t -force_lib
"devel/sage/sage/misc/preparser.py"
sage -t -force_lib "devel/sage/sage/misc/preparser.py"
**********************************************************************
File
"/export/home/drkirkby/sage-4.6.1.alpha2/devel/sage/sage/misc/preparser.py",
line 1484:
sage: z=0; sage.misc.preparser.load(t,globals())
Expected:
Compiling ....pyx...
hi 0
Got:
Compiling /export/home/drkirkby/.sage//temp/laptop/21516//tmp_2.pyx...
Error compiling cython file:
Error compiling /export/home/drkirkby/.sage//temp/laptop/21516//tmp_2.pyx:
running build
running build_ext
building '_export_home_drkirkby__sage_temp_laptop_21516_tmp_2_pyx_0'
extension
creating build
creating build/temp.solaris-2.11-i86pc-2.6
gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall
-Wstrict-prototypes -fPIC
-I/export/home/drkirkby/sage-4.6.1.alpha2/local/include/csage/
-I/export/home/drkirkby/sage-4.6.1.alpha2/local/include/
-I/export/home/drkirkby/sage-4.6.1.alpha2/local/include/python2.6/
-I/export/home/drkirkby/sage-4.6.1.alpha2/local/lib/python2.6/site-packages/numpy/core/include
-I/export/home/drkirkby/sage-4.6.1.alpha2/devel/sage/sage/ext/
-I/export/home/drkirkby/sage-4.6.1.alpha2/devel/sage/
-I/export/home/drkirkby/sage-4.6.1.alpha2/devel/sage/sage/gsl/
-I/export/home/drkirkby/.sage//temp/laptop/21516
-I/export/home/drkirkby/sage-4.6.1.alpha2/local/include/python2.6 -c
_export_home_drkirkby__sage_temp_laptop_21516_tmp_2_pyx_0.c -o
build/temp.solaris-2.11-i86pc-2.6/_export_home_drkirkby__sage_temp_laptop_21516_tmp_2_pyx_0.o
-w -O2
<BLANKLINE>
unable to execute gcc: No such file or directory
error: command 'gcc' failed with exit status 1
<BLANKLINE>
**********************************************************************
File
"/export/home/drkirkby/sage-4.6.1.alpha2/devel/sage/sage/misc/preparser.py",
line 1487:
sage: z
Expected:
-1
Got:
0
**********************************************************************
1 items had failures:
2 of 25 in __main__.example_20
***Test Failed*** 2 failures.
For whitespace errors, see the file
/export/home/drkirkby/.sage//tmp/.doctest_preparser.py
[11.7 s]
----------------------------------------------------------------------
The following tests failed:
sage -t -force_lib "devel/sage/sage/misc/preparser.py"
Total time for all tests: 11.7 seconds
If a test can fail due to the lack of a compiler, does this mean that
to fully utilize a binary install of Sage, the system should have a
development system on it?
The original system this was built on was a Sun Ultra 27 running
OpenSolaris 06/2009 with a full development system installed.
This was then moved to a Sony Vaio laptop, which had a minimal install
of Solaris 11 Express. There was not even a C compiler on this -- it
really ia minimal install from a live CD that allows one to install
Solaris 11 Express too. One would obviously use the package manager to
download the development tools, but I am trying to test Sage without
such tools first, to see what works and what does not.
Apart from this doctest failure, the binary of Sage copied from one OS
to another works fine.
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
