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
for some reason R does not build on a particular system. That user might
be happily using Sage without R installed. Also, Sage itself is used by
certain pieces of the build system (conway_polynomials for example uses
Sage to install a pickle).
> 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 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.
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.
Jeroen.
--
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.
