From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18128 invoked by alias); 21 Jun 2005 22:44:10 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 18120 invoked by uid 22791); 21 Jun 2005 22:44:06 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 21 Jun 2005 22:44:06 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j5LMi4mO023428 for ; Tue, 21 Jun 2005 18:44:04 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j5LMi4u25490; Tue, 21 Jun 2005 18:44:04 -0400 Received: from vpn50-3.rdu.redhat.com (vpn50-3.rdu.redhat.com [172.16.50.3]) by potter.sfbay.redhat.com (8.12.8/8.12.8) with ESMTP id j5LMi1WM001054; Tue, 21 Jun 2005 18:44:02 -0400 Subject: Re: Error building 4.0.1-RC2 From: Eric Christopher To: DJ Delorie Cc: gcc@gcc.gnu.org In-Reply-To: <1119393060.16400.11.camel@dzur.sfbay.redhat.com> References: <20050620054650.GA2377@linux.comp> <1119246588.3334.9.camel@dzur.sfbay.redhat.com> <20050620061224.GA22668@linux.comp> <1119392192.16400.3.camel@dzur.sfbay.redhat.com> <200506212224.j5LMOAS4007383@greed.delorie.com> <1119393060.16400.11.camel@dzur.sfbay.redhat.com> Content-Type: text/plain Date: Tue, 21 Jun 2005 22:44:00 -0000 Message-Id: <1119393839.16400.15.camel@dzur.sfbay.redhat.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SW-Source: 2005-06/txt/msg00958.txt.bz2 On Tue, 2005-06-21 at 15:31 -0700, Eric Christopher wrote: > On Tue, 2005-06-21 at 18:24 -0400, DJ Delorie wrote: > > > Like so? Tested by building outside the source directory and > > > attempting to build in the source directory. Did we want something > > > like this for mainline too? > > > > We've historically put a lot of effort into making "./configure" work, > > so I'd hate to snub anyone willing to work on it. Perhaps an "at the > > moment" in the message might be good. I also changed the error message to read: "... is not supported in this release" Which might work and we can, of course, remove the error message if that ever changes :) OK? -eric