On 2015-09-21 15:04, Jori Mäntysalo wrote:
I don't know exactly what has happened, but at least on my systems compiling is more frequently needed, i.e. sage -b is not enough.
Did you run "make" before (or "make build" if you don't want to wait for the doc)?
You can use "./sage -b" if, since the last time you ran make, you made only changes to the Sage library. Your workflow should look like:
1) checkout ticket or branch 2) make build (or make doc-clean; make) 3) run ./sage or ./sage -t or similar 4) edit Sage library files 5) ./sage -b 6) goto 3 If you're skipping step 2, it's not surprising that bad things happen. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
