Thanks, I think I came to this same conclusion eventually. Now I just have to figure out why building doc also seems to fail more than I want...
[calculus ] Exception occurred: [calculus ] File "ecl.pyx", line 337, in sage.libs.ecl.ecl_safe_eval (sage/libs/ecl.c:4352) [calculus ] RuntimeError: ECL says: Module error: Don't know how to REQUIRE MAXIMA. [calculus ] The full traceback has been saved in /var/folders/k8/nj0z1bkd11dcs1v5hbh_tknc92p43w/T/sphinx-err-LRSqym.log, if you want to report the issue to the developers. I've had more trouble with building doc since the git switch than I can shake a stick at. > -f ntl probably isn't right either, but it's what I'm trying. > > Unfortunately plain 'make' (with SAGE_UPGRADING!=yes) also touches the > files in ... .../installed/, so rerunning 'make' with SAGE_UPGRADING=yes > afterwards has no effect. > > But in your case, it should be sufficent to simply touch > .../installed/ntl-... (the *new* version) [i.e., no need to reinstall > it], and /then/ (re)run 'env SAGE_UPGRADING=yes make'. At least the > errors above, caused by modules still referencing the shared library of > the old NTL version will vanish. > > (You may run into similar problems with other updated spkgs, in which > case the same procedure -- just touching those packages to pretend they > had been installed recently, /after/ any package that depends on them, > and running 'make' with SAGE_UPGRADING set to 'yes' -- should work.) > > -- 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.
