qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "François Revol" <revol@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] c99 or not?
Date: Mon, 18 Aug 2008 00:33:31 +0200 CEST	[thread overview]
Message-ID: <28953775164-BeMail@laptop> (raw)
In-Reply-To: <cef699d70808171522k712671b8g3a256a9a44c20ba@mail.gmail.com>

> 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_vmware.c, as well asm needing to be __asm
> scattered throughout the code.
>
> Thoughts on this?  I already have some prototype code to fix up nbd.c
> and vga_vmware.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çois.

  reply	other threads:[~2008-08-17 22:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17 22:22 [Qemu-devel] c99 or not? Ben Taylor
2008-08-17 22:33 ` François Revol [this message]
2008-08-21 21:58   ` Andreas Färber
2008-08-17 23:28 ` Anthony Liguori
2008-08-17 23:34   ` Ben Taylor
2008-08-21 19:43     ` Andreas Färber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=28953775164-BeMail@laptop \
    --to=revol@free.fr \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).