> On 2015-11-10 18:56, kcrisman wrote: > > Well, it was interrupted for me by a network issue, let's say. But > > then redoing make didn't seem to notice. > I don't understand what you mean with "didn't seem to notice". > > Can you just tell me what you did and what went wrong? I'm a bit lost... >
I started making Sage, sudo make. Then I was disconnected. I returned later and finished making, as far as I know. No errors, other than maybe the "some packages failed to build" with empty message, but then it said "sage build complete". I may have used make or sudo make, I don't remember. But it turned out some packages weren't done at all. Then doing make still didn't finish it. Doing sudo make, so that it could make ~/.sage, did then finally finish the missing packages. So I think that when ~/.sage is not possible to make, Sage doesn't make all packages but still more or less claims to build effectively. Or so I am intuiting. -- 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.
