From owner-freebsd-ports Tue May 23 23:56:00 1995 Return-Path: ports-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA01490 for ports-outgoing; Tue, 23 May 1995 23:56:00 -0700 Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA01484 for ; Tue, 23 May 1995 23:55:57 -0700 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id XAA04046; Tue, 23 May 1995 23:55:49 -0700 Date: Tue, 23 May 1995 23:55:49 -0700 Message-Id: <199505240655.XAA04046@silvia.HIP.Berkeley.EDU> To: gpalmer@westhill.cdrom.com CC: jhs@vector.eikon.e-technik.tu-muenchen.de, ports@FreeBSD.org In-reply-to: <15823.801295025@westhill.cdrom.com> (message from Gary Palmer on Tue, 23 May 1995 22:57:05 -0700) Subject: Re: Sather-1.0.5 From: asami@CS.Berkeley.EDU (Satoshi Asami | =?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=) Sender: ports-owner@FreeBSD.org Precedence: bulk * I'm not sure I follow your conclusions. I just started a build on * westhill (a P5-90 with an obscene ammount of memory) and judging by * the trace I saw, everything up to the * * cd Boot/cs.code; make CC='gcc' CFLAGS='-O2' CS='cs' * * was testing the machine configuration and calculating various bits and * bobs to do with machine-dependant support. Then it gets into the guts * of the compile. Yeah, but Julian's log is missing a lot of lines between "===> Building for..." and "cd Boot/cs.code; ...". Isn't that strange? * Sather is a resource pig. Even on an otherwise idle P5-90, it takes a * long time to even generate the first stage test, and even longer to * run it. I would not be surprised to see it fail on Julian's box, and * it will certainly test the swap code on either thud or Julian's box as * the test executable grows rather large. Ah. So that's probably why it takes an ungodly amount of time on his machine. * Also, Sather 1.0.6 is now out :-) Well, no upgrades now, we are in code freeze.... ;) Satoshi