From owner-freebsd-ports  Tue May 23 21:49:15 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id VAA28659
          for ports-outgoing; Tue, 23 May 1995 21:49:15 -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 VAA28653
          for <ports@FreeBSD.org>; Tue, 23 May 1995 21:49:12 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id VAA03650; Tue, 23 May 1995 21:49:03 -0700
Date: Tue, 23 May 1995 21:49:03 -0700
Message-Id: <199505240449.VAA03650@silvia.HIP.Berkeley.EDU>
To: jhs@vector.eikon.e-technik.tu-muenchen.de
CC: ports@FreeBSD.org
In-reply-to: <199505222249.AAA08181@vector.eikon.e-technik.tu-muenchen.de> (message from Julian Howard Stacey on Tue, 23 May 1995 00:49:18 +0200)
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

 * My spare FreeBSD-current box (a 386)
 * has been chewing on this last line for about 8 hours:
 * 
 * ===>  Building for Sather-1.0.5
 * if [ ! -z "" ]; then  echo "You must turn off the SATHER_COMMANDS environment variable.";  exit 1;  fi
 * cd Boot/cs.code; make CC='gcc' CFLAGS='-O2' CS='cs'
 * gcc -O2 -c globals.c
 * 
 * The box only has 8M,
 * The C file is 430116  bytes
 * one gets a large growing .i file in /var/tmp

Here (on thud), the build goes like this:

=======
===>  Building for Sather-1.0.5
if [ ! -z "" ]; then  echo "You must turn off the SATHER_COMMANDS environment va
riable.";  exit 1;  fi
cd System/GC; make -f 'Makefile' CFLAGS='-O2 -DSILENT' CC='gcc' RANLIB='ranlib'
gcc -O2 -DSILENT -c alloc.c
 :
<lots of lines deleted>
 :
cd Boot/cs.code; make CC='gcc' CFLAGS='-O2' CS='cs'
gcc -O2 -c globals.c
=======

It seems like there is something wrong with the compilation order.
How that can happen, I have no idea.

Satoshi