Starting from a scratch git clone of http://trac.sagemath.org/sage.git, I created a develop branch based on origin/sage and made it (serially !) , getting a sage 6.5beta2 that passes "make testlong" (and "make ptestlong"). End of story ?
Not quite. I learned the following : - The build mechanisms is sensitive to the name of the directory, but - some configuration files do not get rebuilt when this name change. - The build mechanism has problems with intercurrent events (power failure) in some places - "make distclean" is sometimes not enough. - A serial build is necessary in order to be able to use the log file for debugging purposes. This latter point could be helped by redirecting the output of individual makefiles to convenient temporary files, copied to the master log file at end of compilation ; this is (more or less) easy to do under Unix, maybe more problematic under other OSes, if (and when) Sage can be ported to them. The other points necessitate a better understanding of the Sage build mechanisms than mine (which is zilch at the moment...). They need, for the least, some publicizing in the developer's guide... One cold add that they sometimes offset the benefits of git and the "make" mechanism... HTH, -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
