Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sat 25 Oct 2014, 11:19
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
Sage Live - 511 -53
Moderators: Flash, JohnMurga
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
Page 7 of 7 Posts_count   Goto page: Previous 1, 2, 3, 4, 5, 6, 7
Author Message
emil

Joined: 10 Nov 2009
Posts: 618
Location: Austria

PostPosted: Tue 20 Dec 2011, 09:01    Post_subject:  

It works with win 7, I am pretty sure it also works with XP and vista.
I wouldn't be surprised if Win 2000 would work.

The Windows Virtual Box installer is for both 32/64 bit.
During installation it detects which version has to be installed.

I have posted a more detailed "howto create your own Virtual Box exe installer"
http://murga-linux.com/puppy/viewtopic.php?t=73921
It just came to my mind that a similar setup could be used like the venerable "qemu puppy".
Back to top
View user's profile Send_private_message Visit_website 
emil

Joined: 10 Nov 2009
Posts: 618
Location: Austria

PostPosted: Thu 18 Oct 2012, 14:27    Post_subject: Update: Sage Live 511-53  

I am working on a new version which should have some improved functionality:
Download sagelive-511-53.iso

Changelog sagelive-511-53.iso
+ updated sage version to 5.3
+ added Gnutls (for server certificate)
+ added GNU less (replace busybox less, which misses a feature and breaks sage inline help in console mode)
+ added new Personalize settings (from shinobar, replace Countrywizard: cut down the number of pop-up-windows though)
+ updated and fixed system file permissions so this lupu511 version can handle users (in console mode) - still no multiuser puppy
+ included ssh Daemon, so you can log in over the net
+ included preconfigured sage server (with 20 Worker accounts - potential simultanious users over the network)
+ new theme and worked to sort the menus&Desktop (JWM)
- removed Abiword and some Puppy applications (some are still there but not in the menu like gparted)

I dropped Abiword because everytime I need a word processor I ended up installing Libre Office or something (I have an sfs mirrored here).

Most work has gone into the setup of the preconfigured server.
In principle it should be possible to start it and then connect from other computers to the running sage server (with the browser and the IP adress of the server on port 8080).

The Sage server runs as an unprivileged user. It is preconfigured to support a maximum number of 30 simultanious users (using "worker accounts"). For multi user setups it might be necessary to edit the file /home/sageadmin/start_server.sage.

passwords:
Default password for the sage notebook admin account is mathematic.
If you start the sage server it will prompt you for a new password.
Default system passwords are not published (not necessary, because there is autologin)
However it is recommended that you change passwords, especially before you start the ssh daemon (server).
1) open console (as root), type passwd
2) in console (as root) , type passwd sageadmin

hostname
If you missed to set an unique hostname during firstboot:
change hostname in file /etc/hostname (needs reboot)

change ssh keys
you might feel it appropriate to change keys from time to time.
There is an automated script: fix-ssh-keys.sh (run it from terminal)
Back to top
View user's profile Send_private_message Visit_website 
ICPUG

Joined: 24 Jul 2005
Posts: 1290
Location: UK

PostPosted: Fri 19 Oct 2012, 07:58    Post_subject:  

Nearly two years on and this superb specalist puplet is still an active project.

Do you have any feedback from the Sage community, Emil? Is Sage Live used a lot?
Back to top
View user's profile Send_private_message 
emil

Joined: 10 Nov 2009
Posts: 618
Location: Austria

PostPosted: Fri 19 Oct 2012, 09:26    Post_subject:  

Hi ICPUG,

thanks for feedback from an old time follower of this thread.

I have access to the google analytics page of the sage mirrors and there were around 500 downloads of the live cd last month.

I had responses from one university course in Austria, where the Live CD was used as "last stop solution", when students failed to get sage installed otherways.

That was also the reason why I hid some system tools in the current release (like gparted), because not every teacher and sysadmin mightbe happy with handing out those tools. still you can start them from commandline. And it is not the primary scope of this pupplet.

Sage Live CD was used even more, especially there was a time when no good Windows Solution was available for sage. There was a lot of struggle with a port to Cygwin, but ultimatly it was settled that a virtual machine is good enough. With the server you can work in the browser of Windows the same as nativly in Windows. And for programming you can use a ssh shell and work in in the vm directly. Speed loss is not an issue (around 5%). The official sage VM is now based on Fedora and is rather big. I took part in that discussion and I think that is the right solution for sage on Windows (or other exotic OSes).

I am happy that I can manage to sustain the support for this pupplet, maybe I will have also a release next year with an up to date sage version. However probably I will have to update my heavily customized Lupu 511 base then, if time allows ...

I would be very happy to have some feedback if the sage server works - I have not really a big enough LAN to test that properly. It would be even possible to attach the Iso to VirtualBox or so (maybe it is necessary to change network settings to "bridged adapter")

kind regards ,
emil

known bugs:
menu entry for mg (editor) fails. works from comandline
Back to top
View user's profile Send_private_message Visit_website 
saintless


Joined: 11 Jun 2011
Posts: 2580
Location: Bulgaria

PostPosted: Sat 01 Dec 2012, 10:17    Post_subject:  

Hi, Emil,

just some information for people with old computers like mine Smile
(Tested on Gateway E-1400, 600 Mhz, 256Mb RAM).
If you can't start sage console from the start menu or from the desktop icon and when you type sage in urxtv you get this message:
Code:
root@sagepc:~ $sage
----------------------------------------------------------------------
| Sage Version 5.3, Release Date: 2012-09-08                         |
| Type "notebook()" for the browser-based notebook interface.        |
| Type "help()" for help.                                            |
----------------------------------------------------------------------

**********************************************************************
WARNING!  This Sage install was built on a machine that supports
instructions that are not available on this computer.  Sage will
likely fail with ILLEGAL INSTRUCTION errors! The following processor
flags were on the build machine but are not on this computer:

sse2

Email http://groups.google.com/group/sage-support for help.
To remove this warning and make Sage start, just delete
     /sage/local/lib/sage-flags.txt
**********************************************************************
root@sagepc:~ $

this is what you have to do:
Open /sage/local/lib/sage-flags.txt and delete sse2.
Then start sage console.

Thank you for your work with sage and puppy, Emil!
Bets regards!

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send_private_message MSNM 
rasul

Joined: 08 Sep 2012
Posts: 18
Location: Tehran, Iran

PostPosted: Sun 02 Dec 2012, 13:28    Post_subject:  

Hi emil and thanks for your great job, I have used your previous sagelive and now I am managing to use your new one for my dissertation, 50 MB usage of RAM is very fantastic! However, I have also a question. I'm going to run my code on a quad-core machine with 18 GB of RAM, fortunately SageLive supports multicore but does it support also 18 GB of RAM? If not then do you have any suggestion? My code is so heavy that it failed on 4GB Mac Machine, now I want to use my professor's machine and I want to make sure it will work before to tell him I want to work on his machine.

Thanks again.


PS. your previous Sagelive was opening sage notebook directly but the new SageLive first starts a terminal then opens the notebook, is there anyway to bypass the terminal opening in the new sage as well?
Back to top
View user's profile Send_private_message Visit_website 
emil

Joined: 10 Nov 2009
Posts: 618
Location: Austria

PostPosted: Sun 02 Dec 2012, 15:47    Post_subject:  

Hi thanks for feedback,

Saintless, the problem with the old instruction set "should" not happen. can you confirm that sage is running fine (for example run all the included tests with sage --testall.

I compiled sage with the optional flag "SAGE_FAT_BINARIES". This should avoid using the sse2 instruction set. If this error appears I have to look into it (but I have no old machine to test, and ... hrmm, no time). If the tests are fine, maybe there is just a bug throwing the error message.

Hi rasul - thank you for your kind words, it is a honor that you can work with sagelive on your thesis.
I am sorry, but sagelive can not use your modern hardware to full extend, because it is a real 32 bit system and it also uses the original lupu 511'kernel which does not have the PAE feature.
As mentioned above, I see the target more in the low end segment.

In any case to make full use of the hardware of your professor you should install a 64 bit Linux system of your choice and then compile sage natively there. Especially the optimized numeric libaries will run much faster if they can be optimized for multicore and heaps of RAM (e.g. ATLAS library). Compiling sage from source should be mostly painless because they have really good build script and include most of the necessary libraries.

Which OS is already installed on this machine?

about the autostart feature of sage and the terminal - this has escaped me. I thought I had copied the startscript "as is" from the previous version. Again I have to look into it, though it might need some time because I am not "into" it at the moment.

kind regards
emil

all the best
emil
Back to top
View user's profile Send_private_message Visit_website 
saintless


Joined: 11 Jun 2011
Posts: 2580
Location: Bulgaria

PostPosted: Sun 02 Dec 2012, 17:39    Post_subject:  

emil wrote:
Saintless, the problem with the old instruction set "should" not happen. can you confirm that sage is running fine (for example run all the included tests with sage --testall.


Hi, Emil,
this is the output:
Code:

----------------------------------------------------------------------
| Sage Version 5.3, Release Date: 2012-09-08                         |
| Type "notebook()" for the browser-based notebook interface.        |
| Type "help()" for help.                                            |
----------------------------------------------------------------------
sage --testall
sage: sage --testall
---------------------------------------------------------------------------
NameError                                 Traceback (most recent call
last)

/home/mathgeek/<ipython console> in <module>()

NameError: name 'testall' is not defined


If you need any further tests and information for sage on old hardware just write what do you need.

Cheers

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send_private_message MSNM 
emil

Joined: 10 Nov 2009
Posts: 618
Location: Austria

PostPosted: Sun 02 Dec 2012, 18:47    Post_subject:  

Hi,

the command would be from the terminal.
Code:
#sage --testall

it should call "doctests" this means all examples in the documentation of the sourcecode (which has also expected output).
Back to top
View user's profile Send_private_message Visit_website 
rasul

Joined: 08 Sep 2012
Posts: 18
Location: Tehran, Iran

PostPosted: Mon 03 Dec 2012, 01:47    Post_subject:  

Hi emil,

Thanks for the info, it's a pitty i cannot use your distro on that Machine, it's extremely light and as the name suggests your distro can be looked at as only the very sage program in live, too much that the footprint of the distro on the system is small and negligible!

Also thanks for your suggestion, I will miss your distro then for sometimes although i will hopefully follow your great jobs.

Best regards Smile
Back to top
View user's profile Send_private_message Visit_website 
saintless


Joined: 11 Jun 2011
Posts: 2580
Location: Bulgaria

PostPosted: Mon 03 Dec 2012, 02:52    Post_subject:    

emil wrote:
Hi,

the command would be from the terminal.
Code:
#sage --testall

it should call "doctests" this means all examples in the documentation of the sourcecode (which has also expected output).


Hi, Emil,
I guess it is working then, but I get some errors.
I think this one might be because the computer is too slow and I use Seamonkey at the same time:
Code:
sage -t  -force_lib "devel/sage/sage/calculus/calculus.py" 
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***

 [372.0 s]

sage -t  -force_lib "devel/sage/sage/calculus/desolvers.py"
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***

    [372.0 s]

Fullreport:
Code:
root@sagepc:~ $sage --testall
ERROR: File /sage/devel/sage/doc/[a-z][a-z] is missing
ERROR: File /sage/devel/sage/doc/common is missing
sage -t  -force_lib "devel/sage/sage/__init__.py"           
    [0.8 s]
sage -t  -force_lib "devel/sage/sage/algebras/__init__.py" 
    [0.7 s]
sage -t  -force_lib "devel/sage/sage/algebras/affine_nil_temperley_lieb.py"
    [65.0 s]
sage -t  -force_lib "devel/sage/sage/algebras/algebra.py"   
    [39.4 s]
sage -t  -force_lib "devel/sage/sage/algebras/algebra_element.py"
    [36.5 s]
sage -t  -force_lib "devel/sage/sage/algebras/all.py"       
    [36.7 s]
sage -t  -force_lib "devel/sage/sage/algebras/free_algebra.py"
    [44.1 s]
sage -t  -force_lib "devel/sage/sage/algebras/free_algebra_element.py"
    [37.6 s]
sage -t  -force_lib "devel/sage/sage/algebras/free_algebra_quotient.py"
    [39.7 s]
sage -t  -force_lib "devel/sage/sage/algebras/free_algebra_quotient_element.py"
    [38.3 s]
sage -t  -force_lib "devel/sage/sage/algebras/group_algebra.py"
    [86.3 s]
sage -t  -force_lib "devel/sage/sage/algebras/group_algebra_new.py"
    [77.6 s]
sage -t  -force_lib "devel/sage/sage/algebras/iwahori_hecke_algebra.py"
    [71.5 s]
sage -t  -force_lib "devel/sage/sage/algebras/nil_coxeter_algebra.py"
    [112.0 s]
sage -t  -force_lib "devel/sage/sage/algebras/quatalg/__init__.py"
    [1.5 s]
sage -t  -force_lib "devel/sage/sage/algebras/quatalg/all.py"
    [0.6 s]
sage -t  -force_lib "devel/sage/sage/algebras/quatalg/quaternion_algebra.py"
    [140.2 s]
sage -t  -force_lib "devel/sage/sage/algebras/quatalg/quaternion_algebra_cython.pyx"
    [46.8 s]
sage -t  -force_lib "devel/sage/sage/algebras/quatalg/quaternion_algebra_element.pyx"
    [60.8 s]
sage -t  -force_lib "devel/sage/sage/algebras/quaternion_algebra.py"
    [37.8 s]
sage -t  -force_lib "devel/sage/sage/algebras/quaternion_algebra_element.py"
    [54.0 s]
sage -t  -force_lib "devel/sage/sage/algebras/steenrod/__init__.py"
    [2.1 s]
sage -t  -force_lib "devel/sage/sage/algebras/steenrod/all.py"
    [34.4 s]
sage -t  -force_lib "devel/sage/sage/algebras/steenrod/steenrod_algebra.py"
    [184.7 s]
sage -t  -force_lib "devel/sage/sage/algebras/steenrod/steenrod_algebra_bases.py"
    [138.6 s]
sage -t  -force_lib "devel/sage/sage/algebras/steenrod/steenrod_algebra_misc.py"
    [83.4 s]
sage -t  -force_lib "devel/sage/sage/algebras/steenrod/steenrod_algebra_mult.py"
    [83.5 s]
sage -t  -force_lib "devel/sage/sage/all.py"               
    [75.4 s]
sage -t  -force_lib "devel/sage/sage/all_cmdline.py"       
    [75.8 s]
sage -t  -force_lib "devel/sage/sage/calculus/__init__.py" 
    [4.0 s]
sage -t  -force_lib "devel/sage/sage/calculus/all.py"       
    [82.4 s]
sage -t  -force_lib "devel/sage/sage/calculus/calculus.py" 
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***

    [370.2 s]
sage -t  -force_lib "devel/sage/sage/calculus/desolvers.py"
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***

    [372.0 s]
sage -t  -force_lib "devel/sage/sage/calculus/functional.py"
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***

    [368.9 s]


Cheers, Toni

Edit: Testing without Seamonkey to see if there is any difference. I will write the result here soon.

Edit2: It takes too much time on slow computer. I will add the report in another post later. The TIMED OUT errors are not there this time.

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send_private_message MSNM 
emil

Joined: 10 Nov 2009
Posts: 618
Location: Austria

PostPosted: Mon 03 Dec 2012, 05:20    Post_subject:  

Hi Toni-

yep, we can ignore the timeout. However if you leave the testing running it should go on for endless time (about 3 hours on my machine-if it is a very slow computer it coul as well take overnight to run all tests. If there is a real problem with the instruction set, then there should be some wrong results. If it is no problem for you I kindly ask you to try this, The sage folks release new versions in a frenzy and sometimes there are regressions which are not immediately covered.

One of the new features I used in this build was a new compile flag SAGE_ATLAS=base. I am not completly sure how this interacts with SAGE_FAT_BINARIES=yes and as I mentioned I cannot test this myself. cheers emil
Back to top
View user's profile Send_private_message Visit_website 
saintless


Joined: 11 Jun 2011
Posts: 2580
Location: Bulgaria

PostPosted: Mon 03 Dec 2012, 05:49    Post_subject:  

Hi, Emil,
No problem at all. I will wait for sage testing to the end and post the result in text file attached to my next post.
Cheers, Toni

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send_private_message MSNM 
saintless


Joined: 11 Jun 2011
Posts: 2580
Location: Bulgaria

PostPosted: Tue 04 Dec 2012, 10:24    Post_subject:  

Hi, Emil,
here is the errors report::
Code:

The following tests failed:


   /sage/devel/sage/doc/[a-z][a-z] # File not found
   /sage/devel/sage/doc/common # File not found
   sage -t  -force_lib "devel/sage/sage/calculus/desolvers.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/calculus/interpolators.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/calculus/riemann.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/categories/semigroups.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/combinat/root_system/associahedron.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/combinat/root_system/weyl_group.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/combinat/words/paths.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/crypto/mq/mpolynomialsystem.py" # Time out
   sage -t  -force_lib "devel/sage/sage/finance/time_series.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/geometry/lattice_polytope.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/geometry/polyhedron/base.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/geometry/polyhedron/plot.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/geometry/triangulation/element.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/geometry/triangulation/point_configuration.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/graphs/generic_graph.py" # Time out
   sage -t  -force_lib "devel/sage/sage/graphs/graph.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/graphs/graph_generators.py" # Time out
   sage -t  -force_lib "devel/sage/sage/groups/group.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/groups/matrix_gps/general_linear.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/interfaces/ecm.py"
   sage -t  -force_lib "devel/sage/sage/interfaces/gap.py"
   sage -t  -force_lib "devel/sage/sage/interfaces/r.py" # Time out
   sage -t  -force_lib "devel/sage/sage/interfaces/sage0.py" # Time out
   sage -t  -force_lib "devel/sage/sage/interfaces/tachyon.py"
   sage -t  -force_lib "devel/sage/sage/libs/libecm.pyx"
   sage -t  -force_lib "devel/sage/sage/matrix/benchmark.py"
   sage -t  -force_lib "devel/sage/sage/matrix/matrix2.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/matrix/matrix_complex_double_dense.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/matrix/matrix_cyclo_dense.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/matrix/matrix_double_dense.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/matrix/matrix_integer_dense.pyx"
   sage -t  -force_lib "devel/sage/sage/matrix/matrix_integer_dense_hnf.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/matrix/matrix_modn_dense_template.pxi" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/matrix/matrix_rational_dense.pyx"
   sage -t  -force_lib "devel/sage/sage/matrix/matrix_real_double_dense.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/misc/bindable_class.py"
   sage -t  -force_lib "devel/sage/sage/misc/cachefunc.pyx"
   sage -t  -force_lib "devel/sage/sage/misc/citation.pyx"
   sage -t  -force_lib "devel/sage/sage/misc/cython.py"
   sage -t  -force_lib "devel/sage/sage/misc/functional.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/misc/lazy_attribute.py"
   sage -t  -force_lib "devel/sage/sage/misc/preparser.py"
   sage -t  -force_lib "devel/sage/sage/misc/sagedoc.py"
   sage -t  -force_lib "devel/sage/sage/misc/sageinspect.py"
   sage -t  -force_lib "devel/sage/sage/misc/superseded.py"
   sage -t  -force_lib "devel/sage/sage/modular/abvar/abvar.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/abvar/homspace.py"
   sage -t  -force_lib "devel/sage/sage/modular/abvar/torsion_subgroup.py"
   sage -t  -force_lib "devel/sage/sage/modular/arithgroup/congroup_gamma1.py"
   sage -t  -force_lib "devel/sage/sage/modular/buzzard.py"
   sage -t  -force_lib "devel/sage/sage/modular/hecke/algebra.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/hecke/ambient_module.py"
   sage -t  -force_lib "devel/sage/sage/modular/hecke/element.py"
   sage -t  -force_lib "devel/sage/sage/modular/hecke/hecke_operator.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/hecke/module.py"
   sage -t  -force_lib "devel/sage/sage/modular/hecke/submodule.py"
   sage -t  -force_lib "devel/sage/sage/modular/local_comp/local_comp.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/local_comp/type_space.py" # Time out
   sage -t  -force_lib "devel/sage/sage/modular/modform/ambient_g1.py"
   sage -t  -force_lib "devel/sage/sage/modular/modform/constructor.py"
   sage -t  -force_lib "devel/sage/sage/modular/modform/cuspidal_submodule.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/modform/eisenstein_submodule.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/modform/element.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/modform/find_generators.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/modform/numerical.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/modform/space.py" # Time out
   sage -t  -force_lib "devel/sage/sage/modular/modform/tests.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/modsym/ambient.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/modsym/boundary.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/modsym/element.py"
   sage -t  -force_lib "devel/sage/sage/modular/modsym/heilbronn.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/modsym/modsym.py"
   sage -t  -force_lib "devel/sage/sage/modular/modsym/space.py"
   sage -t  -force_lib "devel/sage/sage/modular/modsym/subspace.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/modular/modsym/tests.py"
   sage -t  -force_lib "devel/sage/sage/modular/overconvergent/genus0.py"
   sage -t  -force_lib "devel/sage/sage/modules/free_module.py" # Time out
   sage -t  -force_lib "devel/sage/sage/modules/free_module_element.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/numerical/optimize.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/parallel/decorate.py"
   sage -t  -force_lib "devel/sage/sage/plot/arrow.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/bezier_path.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/circle.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/contour_plot.py" # Time out
   sage -t  -force_lib "devel/sage/sage/plot/disk.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/graphics.py" # Time out
   sage -t  -force_lib "devel/sage/sage/plot/line.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/plot.py" # Time out
   sage -t  -force_lib "devel/sage/sage/plot/plot3d/base.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/plot3d/list_plot3d.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/plot3d/parametric_plot3d.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/plot3d/platonic.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/plot3d/plot3d.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/plot3d/plot_field3d.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/plot3d/revolution_plot3d.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/plot3d/shapes.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/plot3d/shapes2.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/plot/plot3d/tachyon.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/quadratic_forms/quadratic_form__local_representation_conditions.py" # Time out
   sage -t  -force_lib "devel/sage/sage/rings/number_field/number_field.py" # Time out
   sage -t  -force_lib "devel/sage/sage/rings/number_field/number_field_ideal.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/rings/polynomial/multi_polynomial_sequence.py" # Time out
   sage -t  -force_lib "devel/sage/sage/rings/polynomial/pbori.pyx" # Time out
   sage -t  -force_lib "devel/sage/sage/rings/residue_field.pyx" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/sandpiles/sandpile.py" # Time out
   sage -t  -force_lib "devel/sage/sage/schemes/elliptic_curves/ell_field.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/schemes/elliptic_curves/ell_finite_field.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/schemes/elliptic_curves/ell_number_field.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py" # Time out
   sage -t  -force_lib "devel/sage/sage/schemes/elliptic_curves/heegner.py" # Time out
   sage -t  -force_lib "devel/sage/sage/schemes/elliptic_curves/padic_lseries.py" # Time out
   sage -t  -force_lib "devel/sage/sage/schemes/elliptic_curves/sha_tate.py"
   sage -t  -force_lib "devel/sage/sage/schemes/hyperelliptic_curves/hyperelliptic_padic_field.py" # Time out
   sage -t  -force_lib "devel/sage/sage/schemes/toric/chow_group.py"
   sage -t  -force_lib "devel/sage/sage/schemes/toric/variety.py" # Killed/crashed
   sage -t  -force_lib "devel/sage/sage/structure/dynamic_class.py"
   sage -t  -force_lib "devel/sage/sage/structure/element.pyx"
   sage -t  -force_lib "devel/sage/sage/structure/misc.pyx"
   sage -t  -force_lib "devel/sage/sage/structure/sage_object.pyx"
   sage -t  -force_lib "devel/sage/sage/symbolic/expression.pyx" # Time out
   sage -t  -force_lib "devel/sage/sage/tests/benchmark.py"
   sage -t  -force_lib "devel/sage/sage/tests/cmdline.py" # Time out
   sage -t  -force_lib "devel/sagenb-main/sagenb/misc/sageinspect.py"
   sage -t  -force_lib "devel/sagenb-main/sagenb/misc/sphinxify.py"
   sage -t  -force_lib "devel/sagenb-main/sagenb/misc/support.py"
Total time for all tests: 84621.8 seconds
Please see /root/.sage//tmp/test.log for the complete log from this test.
root@sagepc:~ $

Unfortunately I closed the console before reading the last line and I can't give you full log. I attach what I have with copy/paste from console after the end of the test. If you need full log I can do the test again.

Cheers, Toni
somename.tar.gz
Description 
gz

 Download 
Filename  somename.tar.gz 
Filesize  3.11 KB 
Downloaded  299 Time(s) 

_________________
Farewell, Nooby, you will be missed...
Back to top
View user's profile Send_private_message MSNM 
emil

Joined: 10 Nov 2009
Posts: 618
Location: Austria

PostPosted: Wed 05 Dec 2012, 12:44    Post_subject:  

The Killed/crashed errors don't look well, I will post something on the sage channels about the compile flags and maybe I get some explanation. In the meanwhile everybody with a very old chipset should use one of the earlier versions, where the "Fat Binaries" flag is correctly used.
Back to top
View user's profile Send_private_message Visit_website 
Display_posts:   Sort by:   
Page 7 of 7 Posts_count   Goto page: Previous 1, 2, 3, 4, 5, 6, 7
Post_new_topic   Reply_to_topic View_previous_topic :: View_next_topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

Rules_post_cannot
Rules_reply_cannot
Rules_edit_cannot
Rules_delete_cannot
Rules_vote_cannot
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1556s ][ Queries: 13 (0.0073s) ][ GZIP on ]