From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Bw6IY-0006T1-HP for qemu-devel@nongnu.org; Sat, 14 Aug 2004 17:42:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Bw6IW-0006SJ-Tj for qemu-devel@nongnu.org; Sat, 14 Aug 2004 17:42:45 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bw6IW-0006SG-RL for qemu-devel@nongnu.org; Sat, 14 Aug 2004 17:42:44 -0400 Received: from [193.70.192.127] (helo=smtp3.libero.it) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Bw6EG-00026n-BU for qemu-devel@nongnu.org; Sat, 14 Aug 2004 17:38:20 -0400 Received: from localhost (172.16.1.79) by smtp3.libero.it (7.0.027-DD01) id 40D05D0F00D05954 for qemu-devel@nongnu.org; Sat, 14 Aug 2004 23:38:19 +0200 Received: from aquarius (151.30.208.181) by smtp20.libero.it (7.0.027-DD01) id 40E3F8E201E9EB92 for qemu-devel@nongnu.org; Sat, 14 Aug 2004 23:38:19 +0200 Date: Sat, 14 Aug 2004 23:36:01 +0200 From: "Marcello 'R.D.O.' Magnifico" Message-ID: <20040814233601.C1935@aquarius> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: [Qemu-devel] compiling fails, at least one little thing to fix in sources 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 Hi all, I'm trying to compile 0.6.0 official sources from the main site, on a Red Hat 7.3, having seen in the docs that it should have the right tools for the job. GCC complains very shortly about a couple of const and char definitions in vmdk2raw.c and the making stops. Moving definitions up to the beginning of the functions they belong to, seems solving. Have already seen that with sources from different projects, this might be a GCC backport issue, but I remember having seen that on a RH7.2, too. Anyway, I believe this bug should be fixed in the official sources. But, after that, there is another blocking trouble: cpu-exec.c:528: more than 10 operands in `asm'. Anyone has the clue? for this time I don't. Maybe this might open the road to get an even more portable official code, dunno. Too bad I'm no real C programmer, just poking around for fun. yo, RDO