On Jun 27, 9:56 pm, Nils Bruin <nbr...@sfu.ca> wrote: > On Jun 27, 7:41 pm, John H Palmieri <jhpalmier...@gmail.com> wrote: > > > But there is now also a directory spkg/logs/ in which the output for > > each package gets written into a separate file. So you can use those > > for troubleshooting. > > That is not present (does that get cleaned up by make clean?) so > perhaps I didn't do everything that is required for a parallel make.
After looking at the source code, I think that this directory (SAGE_ROOT/spkg/logs) should be there and contain one log file for each spkg regardless of whether you do a parallel build. The relevant code was added in Sage 4.5.alpha0, and it's also possible that it wouldn't be there if you did a "sage -upgrade", only if you built from scratch. Oh, I see looking at your earlier message that you're using 4.4.4. That explains it. Whatever problems you were having had to do with MAKE='make -j4', not SAGE_PARALLEL_SPKG_BUILD. On my Mac, building in parallel (version 4.5.alpha0) with 'make -j2' cut the build time from 140 minutes to 90 minutes. I haven't tried with 'make -j4' because the machine only has 2 cores. I should try that and see what happens. It's more impressive on t2.math.washington.edu, a Solaris machine: without the parallel build, it took me 17 hours, but the parallel build takes under 5 hours. -- John -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
