Hi, all, For the past few releases, I have had a number of odd build failures while building SAGE[*]. Most of them turn out to be essentially EAGAIN failures: fork() fails because I have too many processes running. I bumped up the max processes per user on my system, to 100. This worked for a while, but with 2.5, I ran into the fork problem again.
This means that it takes (up to) roughly 35-40 processes, running simultaneously, to build SAGE. This isn't a complaint, or a bug report :-}; the build process is using all resources it can get. It is worth noting in case you run into mysterious failures, because the build process doesn't always report failures in a way that makes obvious what went wrong. For me, the latest example is 'linbox': the "frickin' slow gsl C- blas" was to be used, but the build failed (too many processes). 'linbox' started to build, but the 'configure' step failed because the expected BLAS support couldn't be found. Since the log of the build process runs to almost 90K lines, it is sometimes easy to miss this kind of failure. Justin [*] On my Dual G5 PowerMac. I am logged in at the console, and typically have lots of processes running. -- Justin C. Walker, Curmudgeon at Large Institute for the Absorption of Federal Funds ----------- My wife 'n kids 'n dogs are gone, I can't get Jesus on the phone, But Ol' Milwaukee's Best is my best friend. ----------- --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-forum URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
