> On 2015-11-10 07:25, kcrisman wrote: > > If the build is interrupted, bad things will happen without errors. > What do mean? Do you think that Sage should check that all packages are > installed before starting? I don't think we should do that: imagine that >
No, that's not what I meant. I meant Sage shouldn't tell me it built okay when it didn't. > > > and/or you can't write to HOME/.sage > Well, that's a different thing entirely. If no error message shows up, > this is indeed a problem with the build scripts. > > I get an error, but it doesn't tell me any packages failed to build. > > I had > > reissued make and the build completed, including building > > documentation! Or so it said, anyway. It never noticed the missing > > packages. > I don't get it. You said you *interrupted* the build. > > Well, it was interrupted for me by a network issue, let's say. But then redoing make didn't seem to notice. > Bizarrely, doing "sudo make" so it could write to my local folder FIRST > > rebuilt the documentation (quick because no changes) and THEN just now > > started building cddlib, gfan, cvxopt, and a host of other stuff. I > > will repeat that there were no relevant error messages in the log files. > Yes, this order is optimized for parallel builds. With parallel builds, > you want to start building the documentation as soon as possible since > it takes a long time. > > > Okay, that's newer - in the past the documentation was always the last to build. Good idea, as you say. -- 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.
