From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:34248) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRw4r-00086Y-Pr for qemu-devel@nongnu.org; Tue, 08 May 2012 21:52:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SRw4q-00020j-0L for qemu-devel@nongnu.org; Tue, 08 May 2012 21:52:29 -0400 Received: from e4.ny.us.ibm.com ([32.97.182.144]:50886) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SRw4p-000204-SV for qemu-devel@nongnu.org; Tue, 08 May 2012 21:52:27 -0400 Received: from /spool/local by e4.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 8 May 2012 21:52:23 -0400 Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id B67A56E8054 for ; Tue, 8 May 2012 21:52:20 -0400 (EDT) Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q491qKXj077160 for ; Tue, 8 May 2012 21:52:20 -0400 Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q491qJ6h028553 for ; Tue, 8 May 2012 21:52:20 -0400 Message-ID: <4FA9CDD1.4050105@us.ibm.com> Date: Tue, 08 May 2012 20:52:17 -0500 From: Anthony Liguori MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] qemu-1.0-rc1 delayed (need fix for PPC32 build) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel Cc: Blue Swirl , Alexander Graf , =?ISO-8859-1?Q?Andreas_F=E4rber?= Hi, I was hoping we'd have a solution by now but it looks like we don't. I'm going to delay the qemu-1.0-rc1 release until tomorrow. I'd like to propose a couple paths forward. Here's my understanding of the situation: 1) TCG changes were made for the Sparc/Alpha targets that use AREG0 2) AREG0 never worked properly on ppc32 hosts 3) Until recently, this caused a runtime failure of the Sparc/Alpha targets on ppc32. However, malc recently changed this to a build time failure. I don't feel comfortable shipping a release candidate with a known failing build. Here are the options: a) Revert malc's change. I don't think this is much better than shipping a broken build. b) Disable sparc/alpha targets in default_target_list on ppc32 hosts. I think is probably the best short term approach. c) Wait for Andreas' patches (I believe Alex detected a problem in the current version). Unless anyone strongly objects, I'm going to implement (b) tomorrow morning so we can keep the -rc cycle moving. I would hope that we'll have something worked out for (c) by -rc2. Regards, Anthony Liguori