From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KUqn8-0003tp-Mu for qemu-devel@nongnu.org; Sun, 17 Aug 2008 18:32:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KUqn7-0003st-PD for qemu-devel@nongnu.org; Sun, 17 Aug 2008 18:32:06 -0400 Received: from [199.232.76.173] (port=39776 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KUqn7-0003sk-94 for qemu-devel@nongnu.org; Sun, 17 Aug 2008 18:32:05 -0400 Received: from smtp8-g19.free.fr ([212.27.42.65]:58924) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KUqn6-0007rt-UT for qemu-devel@nongnu.org; Sun, 17 Aug 2008 18:32:05 -0400 Received: from smtp8-g19.free.fr (localhost [127.0.0.1]) by smtp8-g19.free.fr (Postfix) with ESMTP id D61BE32A81C for ; Mon, 18 Aug 2008 00:31:57 +0200 (CEST) Received: from laptop (vaf26-2-82-244-111-82.fbx.proxad.net [82.244.111.82]) by smtp8-g19.free.fr (Postfix) with ESMTP id BC74232A80E for ; Mon, 18 Aug 2008 00:31:57 +0200 (CEST) In-Reply-To: Subject: Re: [Qemu-devel] c99 or not? From: "=?windows-1252?q?Fran=E7ois?= Revol" Date: Mon, 18 Aug 2008 00:33:31 +0200 CEST Message-Id: <28953775164-BeMail@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable 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 > I've been hacking about on qemu again on Solaris 10, which I've run > into an issue. > > in the nbd.h file, it includes stdbool.h, but on Solaris 10, you have > to enable c99 > to get this to compile. > > This has a rather nasty set of cascading effects, most of which are > anonymous > unions in nbd.c and vga=5Fvmware.c, as well asm needing to be =5F=5Fasm > scattered throughout the code. > > Thoughts on this=3F I already have some prototype code to fix up nbd.c > and vga=5Fvmware.c to get rid of the anonymous unions, but will have > some > more work to complete to get a working compile. > As a BeOS and Haiku dev, I'm used to having to "fix" apps back to c89 to get them working with gcc2 because we are forced to stick to it due to the C++ ABI breackage. Haiku shall also provice gcc4 soon, and it might be possible to get gcc4 usable under BeOS, but it's like hunting a fly with a hand grenade. Now, I didn't try to build QEMU on BeOS for quite some time, not even sure it'd still build. I don't know if Mickael Lotz (BeOS port maintainer IIRC) has recent builds either. Still, avoiding C99 if possible would help, and possibly other platforms. Fran=E7ois.