From owner-freebsd-ports Wed Jan 30 13:40: 8 2002 Delivered-To: freebsd-ports@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C2ABF37B402 for ; Wed, 30 Jan 2002 13:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0ULe1W01056; Wed, 30 Jan 2002 13:40:01 -0800 (PST) (envelope-from gnats) Date: Wed, 30 Jan 2002 13:40:01 -0800 (PST) Message-Id: <200201302140.g0ULe1W01056@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: "Scot W. Hetzel" Subject: Re: ports/34459: Dumping config.log on configure error is unintuitive. Reply-To: "Scot W. Hetzel" Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR ports/34459; it has been noted by GNATS. From: "Scot W. Hetzel" To: "Thomas Hurst" , Cc: Subject: Re: ports/34459: Dumping config.log on configure error is unintuitive. Date: Wed, 30 Jan 2002 15:35:24 -0600 From: "Thomas Hurst" > When configure fails, bsd.port.mk dumps config.log to the > terminal. This typcially results in several thousand lines of > crap which often hides the actual problem way up in the display > buffer, assuming it extends that far up. > > It should either pipe it through a pager, tail the last 20 lines > or so (since that'll be where it failed anyway), or be made > optional. bsd.port.mk doesn't dump the contents of the config.log. config.log is dumped by the configure script in the work/ directory. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message