From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JZuxa-0004qS-3v for qemu-devel@nongnu.org; Thu, 13 Mar 2008 17:27:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JZuxY-0004qG-67 for qemu-devel@nongnu.org; Thu, 13 Mar 2008 17:27:33 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JZuxY-0004qD-2O for qemu-devel@nongnu.org; Thu, 13 Mar 2008 17:27:32 -0400 Received: from el-out-1112.google.com ([209.85.162.183]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JZuxX-0001iZ-Q8 for qemu-devel@nongnu.org; Thu, 13 Mar 2008 17:27:31 -0400 Received: by el-out-1112.google.com with SMTP id y26so2244528ele.8 for ; Thu, 13 Mar 2008 14:27:30 -0700 (PDT) Message-ID: Date: Thu, 13 Mar 2008 17:27:29 -0400 From: "Ben Taylor" Subject: Re: [Qemu-devel] CVS build error In-Reply-To: <200803132047.21270.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_20350_20949234.1205443649630" References: <200803131533.46989.rickv@hobi.com> <200803132047.21270.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_20350_20949234.1205443649630 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Thu, Mar 13, 2008 at 4:47 PM, Paul Brook wrote: > > gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2) > > Which part of "gcc 4.x is not supported" didn't you understand? > > Paul > > > Apparently, we should make configure fail horribly if gcc4 is found even if disable-gcc-check is enabled. ------=_Part_20350_20949234.1205443649630 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Thu, Mar 13, 2008 at 4:47 PM, Paul Brook <paul@codesourcery.com> wrote:
> gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2)

Which part of "gcc 4.x is not supported" didn't you understand?

Paul


Apparently, we should make configure fail horribly if gcc4 is found even
if disable-gcc-check is enabled.
------=_Part_20350_20949234.1205443649630--