From owner-freebsd-ports Thu Aug 31 14: 2:24 2000 Delivered-To: freebsd-ports@freebsd.org Received: from mail3.aracnet.com (mail3.aracnet.com [216.99.193.38]) by hub.freebsd.org (Postfix) with ESMTP id D28BC37B422; Thu, 31 Aug 2000 14:02:22 -0700 (PDT) Received: from mephistopheles. (max3-208-11.cust.aracnet.com [216.99.208.11]) by mail3.aracnet.com (8.11.0/8.11.0) with ESMTP id e7VL2PH10579; Thu, 31 Aug 2000 14:02:25 -0700 Date: Thu, 31 Aug 2000 14:02:19 -0700 (PDT) From: Scott Flatman X-Sender: sf@mephistopheles. To: "Bruce A. Mah" Cc: freebsd-ports@FreeBSD.ORG Subject: Re: gmake port broken In-Reply-To: <200008312051.e7VKpOP08186@bmah-freebsd-0.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 31 Aug 2000, Bruce A. Mah wrote: > Can you give more information, like what version of FreeBSD you're > running? I just finished a build of the gmake-3.79.1 port and it went > just fine (running 4-STABLE built earlier this > week). DOH! I'm running 5.0-current last cooked on Aug 28 2000. I can build gmake fine on it's own, just not with the ports collection. > (I suspect that your problem might be fixed if you do a "make clean" in > the directory where the gmake port lives before building. It doesn't > look to me like you did this, and if there was some old cruft lying > around from a prior build, it could interfere with the build you're > trying to do.) This morning I pulled down a fresh copy of the entire ports collection just to be sure, so yeah, a "make clean" was done. :) Thanks. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message