From owner-freebsd-ports Wed Jan 30 15:40: 5 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 B5BEF37B419 for ; Wed, 30 Jan 2002 15:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0UNe2728013; Wed, 30 Jan 2002 15:40:02 -0800 (PST) (envelope-from gnats) Date: Wed, 30 Jan 2002 15:40:02 -0800 (PST) Message-Id: <200201302340.g0UNe2728013@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Alan Eldridge Subject: Re: ports/34459: Dumping config.log on configure error is unintuitive. Reply-To: Alan Eldridge 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: Alan Eldridge To: FreeBSD Ports List Cc: Subject: Re: ports/34459: Dumping config.log on configure error is unintuitive. Date: Wed, 30 Jan 2002 18:37:13 -0500 This is nasty. Somebody please patch this out, or at least give it a knob that defaults to 'no'. I'm sorry to be so blunt, but dumping config.log in its entirety sucks really hard. -- Alan E "Please rush me my portable walrus cleaning kit! Yes I am over 18, but my IQ isn't." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message