> > I wonder if he has enough RAM? Maybe gcc does dumb things > > when there isn't enough ram sometimes. > > Well, I would assume that the OOM killer might do something stupid. If > malloc fails inside gcc I would expect it to die gracefully. Maybe > Phil should check /var/log/messages for any signs of the OOM killer.
Indeed, thanks for the tips. Both machines were vservers with 1Gb RAM and both were running the Sage 2.10.3 notebook during the compilation, so apparently one of the notebook was more hungry. I stopped the notebook and now it seems to compile fine (but still running for probably a couple of hours...). BTW the "make test" finished on the first machine with an "all passed", good job! ;-) Phil --~--~---------~--~----~------------~-------~--~----~ 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-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
