> Aside from that it is *highly* > recommended to build from source if you are developing since mixing > and matching different compiler releases [even on OSX] can lead to odd > results, i.e. Heisenbugs and segfaults.
Maybe a note to that effect should be put on the download page, or in the README on the binary pages? At the moment we really don't encourage people to build from source at all. -M. Hampton On May 8, 7:14 am, mabshoff <[EMAIL PROTECTED]> wrote: > On May 8, 12:21 am, John H Palmieri <[EMAIL PROTECTED]> wrote: > > > On May 7, 1:19 pm, mhampton <[EMAIL PROTECTED]> wrote: > > > > I wonder what version the "30 seconds" comment was from. The code > > > base is probably growing faster than processor/hard drive speeds. > > > > On my Macbook, 2.4 Ghz intel chip, 5400rpm drive, a first clone of 3.0 > > > takes about 1 minute, the second clone 30 seconds. > > > This is from a brand-new, just downloaded, binary build? > > Aside from all the other issues: You should *always* rebuild the Sage > library of a binary build before running clone. Otherwise each clone > requires a complete rebuild. Aside from that it is *highly* > recommended to build from source if you are developing since mixing > and matching different compiler releases [even on OSX] can lead to odd > results, i.e. Heisenbugs and segfaults. > > Cheers, > > Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
