On Nov 23, 2007 8:18 PM, Justin C. Walker <[EMAIL PROTECTED]> wrote: > > This is all really weird since I fully tested building Sage-2.8.13 on > > OSX 10.4 intel and OSX 10.5 intel (both core duo and Xeon), > > and didn't have any problems at all. So the problem could > > be with... ... > I reported this during one of the "alpha/rc" cycles (2.8.10.alpha?, I > think), and tried the "move /usr/local out of the way" trick. That
I see! The problem was definitely in 2.8.13.rc0 I think, because I found it then, and then somebody subsequently fixed it as a result, i.e., the problem is fixed in 2.8.13 (but not before). > > Something I've wondered about for a while -- is there a bulletproof > > way to ignore /usr/local/ during build of Sage? > > I think 'gcc' has flags that let you force the lookup paths for > "system-supplied" includes and libs. I'll see if I can track that down. That would be very very interesting indeed. -- William --~--~---------~--~----~------------~-------~--~----~ 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
