Gentoo Archives: gentoo-science

From: "François Bissey" <f.r.bissey@×××××××××.nz>
To: gentoo-science@l.g.o
Subject: [gentoo-science] [sage-on-gentoo] updates
Date: Fri, 21 May 2010 05:41:05
Message-Id: 201005212240.38631.f.r.bissey@massey.ac.nz
1 Hi all,
2
3 sage-4.4.2 has just been released. I am guessing that Christopher
4 may be preparing for exams in June so I will probably do the bump.
5 I have already bumped sage-doc.
6
7 Other matters:
8 -The situation on amd64 is still bad. There has been a silent (no revbump)
9 update to cython to deal with a strict-aliasing problem:
10 http://bugs.gentoo.org/show_bug.cgi?id=294585
11 I don't have the hardware so I cannot check if it has an influence on our
12 problems but it is worth a try.
13
14 -python-2.6.5-r2 is going stable. sage is of course still shipping 2.6.4.
15 I have already put a "pickled" version of python-2.6.5-r2 in the overlay
16 (2.6.5-r99). Apart from:
17 http://github.com/cschwan/sage-on-gentoo/issues#issue/1
18 which needs to be fixed in sage (patch/suggestions welcome) I don't expect
19 any problems with that.
20
21 -mpir-2.0.0 entered the overlay, sage is actually still shipping 1.2.2.
22 Report problems as usual.
23
24 -I have tracked 2 other failing tests which are now working:
25 http://github.com/cschwan/sage-on-gentoo/issues#issue/8
26 http://github.com/cschwan/sage-on-gentoo/issues#issue/9
27
28 -I am wondering if issues 3 and 6 are down to -ffast-math in one way
29 or another. If you have any similar issues please post.
30
31 -still no clue on gap's behaviour. Considering the amount of aliasing problem
32 you may as well try to add -fno-strict-aliasing to your CFLAGS for building
33 gap and see if that improve things.
34
35 -I have imported sympy-0.6.6 in the overlay as it has left the portage tree
36 and sage currently doesn't work with 0.6.7. We should investigate doing
37 some porting work. Porting work to scipy-0.7.2 would be a good idea too.
38
39 Francois

Replies

Subject Author
Re: [gentoo-science] [sage-on-gentoo] updates Steven Trogdon <strogdon@×××××.edu>