From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12957 invoked by alias); 14 May 2002 12:06:05 -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 12943 invoked by uid 71); 14 May 2002 12:06:04 -0000 Date: Tue, 14 May 2002 05:06:00 -0000 Message-ID: <20020514120604.12942.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Josef Spillner Subject: Re: bootstrap/6622: configure should fail if bison is not found Reply-To: Josef Spillner X-SW-Source: 2002-05/txt/msg00378.txt.bz2 List-Id: The following reply was made to PR bootstrap/6622; it has been noted by GNATS. From: Josef Spillner To: "Joseph S. Myers" Cc: , Subject: Re: bootstrap/6622: configure should fail if bison is not found Date: Tue, 14 May 2002 13:59:38 +0200 On Saturday 11 May 2002 02:22, Joseph S. Myers wrote: > This is not appropriate for building from release tarballs, which inclu= de > 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? :-= ) Anyway, I found there's more or less the same bug report already at=20 other/2529, so both should be closed then. Josef