All tests passed for me on two Intel macs, running os x 10.4 and 10.5. -M. Hampton
On Jun 17, 11:53 am, mabshoff <[EMAIL PROTECTED]> wrote: > On Jun 17, 9:22 am, "John Cremona" <[EMAIL PROTECTED]> wrote: > > > Built 3.0.3.rc0 on here: > > Hi John, > > > Linux version 2.6.24-18-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 > > (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed May 28 20:27:26 UTC 2008 > > > and here: > > > Linux version 2.6.18.8-0.3-default ([EMAIL PROTECTED]) (gcc version > > 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Tue Apr 17 08:42:35 > > UTC 2007 > > > with all tests passes ok. > > Thanks for testing. > > > The first of those is my new laptop: > > processor : 1 > > vendor_id : GenuineIntel > > cpu family : 6 > > model : 23 > > model name : Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz > > stepping : 6 > > cpu MHz : 800.000 > > cache size : 3072 KB > > > so I was surprised that the build took 3h31m. Is there an easy way of > > telling from the 240k line install.log what was taking the time? > > Run > > [EMAIL PROTECTED]:/scratch/mabshoff/release-cycle/sage-3.0.3.rc0$ grep > "real" install.log | grep "[0-9]s" | grep "[0-9]m" > real 0m0.099s > real 0m0.014s > real 1m9.018s > real 0m0.626s > real 0m20.608s > real 0m44.511s > real 6m17.188s > real 7m34.272s > real 0m0.017s > real 0m0.049s > real 0m0.139s > real 0m6.509s > real 0m2.422s > real 1m9.439s > real 0m14.262s > real 0m39.645s > real 0m19.183s > real 1m26.368s > real 0m15.630s > real 2m22.221s > real 1m9.520s > real 0m17.162s > real 0m1.177s > real 0m2.378s > real 0m38.038s > real 14m7.341s > real 2m36.160s > real 0m19.094s > real 0m0.628s > real 0m44.127s > real 2m47.387s > real 0m17.999s > real 0m14.231s > real 1m16.641s > real 2m2.297s > real 0m2.438s > real 0m41.097s > real 0m16.610s > real 0m0.110s > real 0m9.385s > real 0m0.517s > real 0m3.658s > real 0m19.933s > real 0m0.679s > real 0m11.350s > real 0m0.467s > real 0m7.670s > real 9m19.472s > real 0m0.775s > real 13m47.986s > real 0m18.168s > real 7m19.461s > real 0m1.275s > real 0m1.275s > real 4m21.959s > real 0m22.737s > real 0m12.575s > real 0m12.771s > real 0m57.792s > real 46m16.674s > real 0m0.941s > real 0m0.068s > real 1m4.336s > real 5m2.869s > real 2m26.173s > real 0m4.440s > real 0m54.292s > real 0m8.770s > real 0m9.618s > real 0m40.524s > real 0m7.250s > real 0m0.558s > real 0m1.754s > real 0m25.731s > real 0m1.990s > real 0m0.293s > real 5m41.744s > real 0m26.759s > real 1m30.218s > real 0m0.105s > real 0m0.950s > real 0m2.810s > real 0m0.014s > real 156m27.415s > real 43m1.967s > real 2m18.279s > real 2m26.443s > real 2m13.284s > > And then take a look for large times. Once you found the culprit jump > into install.og and search for the string and scroll up until you see > the spkg being unpacked. In this case I suspect that ATLAS is at fault > since its build time even with tuning depends on the cache size. I.e. > on the Itaniums we build ATLAS alone takes 3 hours to compile since > they have massive caches. > > > John > > Also: Thanks Jaap for testing :) > > Cheers, > > Michae; --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
