Date: Wed, 30 Jan 2002 14:50:02 -0800 (PST) From: Thomas Hurst <freaky@aagh.net> To: freebsd-ports@FreeBSD.org Subject: Re: ports/34459: Dumping config.log on configure error is unintuitive. Message-ID: <200201302250.g0UMo2p16744@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: Thomas Hurst <freaky@aagh.net>
To: "Scot W. Hetzel" <hetzels@westbend.net>
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: ports/34459: Dumping config.log on configure error is unintuitive.
Date: Wed, 30 Jan 2002 22:43:00 +0000
* Scot W. Hetzel (hetzels@westbend.net) wrote:
> 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.
Um, line 2270:
${CONFIGURE_ENV} ./${CONFIGURE_SCRIPT} ${CONFIGURE_ARGS}; then \
${ECHO} "===> Script \"${CONFIGURE_SCRIPT}\" failed: here are the contents of \"${CONFIGURE_LOG}\""; \
${CAT} ${CONFIGURE_LOG}; \
${ECHO} "(end of \"${CONFIGURE_LOG}\")"; \
--
Thomas 'Freaky' Hurst - freaky@aagh.net - http://www.aagh.net/
-
Binary, adj.:
Possessing the ability to have friends of both sexes.
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?200201302250.g0UMo2p16744>