> > > Sadly, the update pulse for the stats at 9:03 is missing, but I doubt that > > > it's a matter of too less memory as aahz has 1.1 GB of swap. > > What do these numbers tell me? Aahz crashed, the last change to the log file > > was at 0919: > > -rw-r--r-- 1 buildd buildd 8328 Jan 21 09:19 > > logs/mcmcpack_0.8-1-1_20070121-0903 > > It tells you that (for some reason) the problem is unlikely RAM related. > That's what I read out of the data. Eating 1 GB of swap is nothing a m68k > can do rather quick under normal circumstances... > Alas, the build of r-base is known to require a lot of RAM. That's why I > filed a bug against r-base some time ago...
I forgot: all R related build failures usually only happen on 060. kullervo just got stuck with r-cran-eco_3.0-2-1 (rescheduling on q650). Gotta be something specific to the 060 (integer or floating point emulation? Subtle cross-gcc bug?). What machine did r-base get built on last time? Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]