On 15/08/2008, at 12:49 PM, David Philp wrote:
> > Hi > >>> I forgot to mention that this is boost 1.35.0. I assume it is a >>> difference between the boosts, because sage is unlikely to have >>> changed without you noticing. I am now compiling sage 3.0.3 and >>> 3.0.6 >>> with the --enable-framework, to see what happens. I will also try >>> 1.35.0 against vanilla 3.0.6. >> >> Ok, please let me know how it goes. > > * 3.0.6 failed to compile. Some problem I didn't want to chase down. I figured out why 3.0.6 failed to compile with the --enable-framework option. Originally, I compiled 3.0.3 without that option, and it presumably set up everything required by sage. When I recompiled with the --enable-framework, that did not delete files put in place by the original compilation. When I compiled 3.0.6 with the --enable-framework option, it was the first time and there were no such redundant files. I will compare vanilla and vanilla+framework builds of 3.0.3, that might give a feeling for whether it is sensible to support framework builds out of the box. D --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
