qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Eduardo Felipe" <edusaper@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows build broken
Date: Wed, 12 Dec 2007 11:41:00 +0100	[thread overview]
Message-ID: <83a4d4ca0712120241n77b602a3v22990b2bb12ca4e2@mail.gmail.com> (raw)
In-Reply-To: <BAY133-DAV521037E9AFD28300472F2B9650@phx.gbl>

[-- Attachment #1: Type: text/plain, Size: 517 bytes --]

2007/12/12, C.W. Betts <computers57@hotmail.com>:
>
> Same problem with cygwin.  I think it's a problem with BlockInterfaceType
> not being correctly parsed on mingw-gcc for some odd reason.



Hi,

I don't think it is related with BlockInterfaceType itself. The problem is
to use "interface" as a variable or parameter name, which seems to be
confused with a reserved keyword, type or something like that. I was able to
compile with mingw changing that variable name and all its references along
the code.

Regards.

[-- Attachment #2: Type: text/html, Size: 812 bytes --]

  reply	other threads:[~2007-12-12 10:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12  3:05 [Qemu-devel] Windows build broken Balazs Attila-Mihaly (Cd-MaN)
2007-12-12 10:08 ` C.W. Betts
2007-12-12 10:41   ` Eduardo Felipe [this message]
2007-12-12 15:27     ` C.W. Betts
2007-12-12 19:50       ` Eduardo Felipe
2007-12-12 20:54         ` Stefan Weil
2007-12-13  0:47           ` JonY
2007-12-13 20:20             ` [Qemu-devel][Patch] " Stefan Weil
2007-12-14  1:39               ` JonY
2007-12-14 19:05                 ` Stefan Weil
2007-12-16 13:54                   ` Paul Brook
  -- strict thread matches above, loose matches on Subject: below --
2005-07-12  6:05 [Qemu-devel] ^[$B!y!z0lK|1_J,%W%l%<%s%H!z!y^[(B info
2005-07-12 16:20 ` [Qemu-devel] Windows build broken Andreas Bollhalder
2005-07-13 20:14   ` Andreas Bollhalder

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=83a4d4ca0712120241n77b602a3v22990b2bb12ca4e2@mail.gmail.com \
    --to=edusaper@gmail.com \
    --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).