Date: Wed, 30 Jan 2002 13:40:01 -0800 (PST) From: "Scot W. Hetzel" <hetzels@westbend.net> To: freebsd-ports@FreeBSD.org Subject: Re: ports/34459: Dumping config.log on configure error is unintuitive. Message-ID: <200201302140.g0ULe1W01056@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/34459; it has been noted by GNATS. From: "Scot W. Hetzel" <hetzels@westbend.net> To: "Thomas Hurst" <freaky@aagh.net>, <FreeBSD-gnats-submit@FreeBSD.ORG> 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" <freaky@aagh.net> > 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/<distname> directory. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201302140.g0ULe1W01056>