On 07/09/12 08:45, John W. Foster wrote:
Jan: I did as you suggested & restarted the compiling process on my system. I did have to restart it 2 times to get it to finish, but I do have it running now and it appears fine. I will be testing it out and look forward to the final release. Thanks for the tip on restarting the compile. I now need to determine why it segfaulted out twice during this effort. I would appreciate any ideas on that. Debian-AMD-64 stable system Thanks frosty
I have had experience of a sage build failing because of the error "too many files open." This is using FreeBSD with an i5. Then I restart the build, and it works just fine. I think I was overloading the system. It was always in the build of python that the problem happened. I don't know if this is related to your problem.
What I do is to look at the directories in sage-*/spkg/builds to see which packages didn't build, and then look inside sage-*/spkg/logs to look at that particular log file to see exactly where the error took place.
-- -- 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
