2010/1/4 Jaap Spies <j.sp...@hccnet.nl>: > Dr. David Kirkby wrote: >> Jaap Spies wrote: >> >>> As you stated before many spkgs are not in a good shape to handle this. > >>> Jaap >> >> I've raised tickets for some of these simple spkg-install fixes. >> >> >> opencdk >> http://trac.sagemath.org/sage_trac/ticket/7817 >> >> freetype: >> http://trac.sagemath.org/sage_trac/ticket/7138 >> >> flint >> http://trac.sagemath.org/sage_trac/ticket/7815 >> >> ecllib: >> http://trac.sagemath.org/sage_trac/ticket/7814 >> >> python: >> http://trac.sagemath.org/sage_trac/ticket/7761 >> >> gd >> http://trac.sagemath.org/sage_trac/ticket/7162 >> >> Perhaps you would try some of them out and review them. They are all pretty >> minor changes. >> > > Some made it in sage-4.3.1.alpha0!
Yes, several in fact. > I made a list of files containing SAGE64 in spkg-install and elsewhere. > > > > See: http://boxen.math.washington.edu/home/jsp/standard_spkgs_with_SAGE64 > > The build of sage-4.3.1.alpha0 fails on python an after that on mpir-1.2.2. > Don't know how to solve that. I leave that to you :) > > Jaap OK. It it worth doing a 'make -k' which will build the packages, but continue if they fail. `Then we can get a list of the dodgy packages. Obviously some will fail as what they depend on has failed, but it is still useful 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
