From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28142 invoked by alias); 15 May 2002 18:46:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 28126 invoked by uid 71); 15 May 2002 18:46:00 -0000 Date: Wed, 15 May 2002 11:46:00 -0000 Message-ID: <20020515184600.28125.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Phil Edwards Subject: Re: bootstrap/6622: configure should fail if bison is not found Reply-To: Phil Edwards X-SW-Source: 2002-05/txt/msg00429.txt.bz2 List-Id: The following reply was made to PR bootstrap/6622; it has been noted by GNATS. From: Phil Edwards To: Josef Spillner Cc: "Joseph S. Myers" , gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: bootstrap/6622: configure should fail if bison is not found Date: Wed, 15 May 2002 14:43:30 -0400 On Tue, May 14, 2002 at 01:59:38PM +0200, Josef Spillner wrote: > On Saturday 11 May 2002 02:22, Joseph S. Myers wrote: > > This is not appropriate for building from release tarballs, which include > > the Bison-generated files so that users don't need Bison installed. > > Uhm, so what is the point of having this check in configure.in at all? :-) First, even developers make mistakes. If a developer is trying to build from scratch on a new machine, this ensures that all the required tools are in place. Second, the check is more than just for existence; it's also for the pathname. -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen. - Samuel Adams