qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefan Hajnoczi <stefanha@redhat.com>, Stefan Weil <sw@weilnetz.de>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] dataplane build error
Date: Thu, 03 Jan 2013 12:59:44 -0600	[thread overview]
Message-ID: <87y5ganlcv.fsf@codemonkey.ws> (raw)
In-Reply-To: <20130103094457.GB28326@stefanha-thinkpad.muc.redhat.com>

Stefan Hajnoczi <stefanha@redhat.com> writes:

> On Thu, Jan 03, 2013 at 10:32:43AM +0100, Stefan Weil wrote:
>> Am 03.01.2013 10:30, schrieb Gerd Hoffmann:
>> >   CC    hw/dataplane/vring.o
>> >cc1: warnings being treated as errors
>> >/home/kraxel/projects/qemu/hw/dataplane/vring.c: In function ‘vring_setup’:
>> >/home/kraxel/projects/qemu/hw/dataplane/vring.c:46: error: implicit
>> >declaration of function ‘trace_vring_setup’
>> >/home/kraxel/projects/qemu/hw/dataplane/vring.c:46: error: nested extern
>> >declaration of ‘trace_vring_setup’
>> >gmake: *** [hw/dataplane/vring.o] Error 1
>> 
>> 
>> Hi Gerd,
>> 
>> I got this one, too. Removing a generated file trace.h fixes it.
>
> Anthony hit this yesterday with an out-of-tree build, too.

http://article.gmane.org/gmane.comp.emulators.qemu/186471

I usually try to make an announcement when there are issues like this.

Regards,

Anthony Liguori

>
> trace.h used to be generated, since
> eac236ea7bfc1902126be70459e320591078df5c (build: Use separate makefile
> for "trace/") it is a static file.  The build system is getting
> confused.
>
> Stefan

      reply	other threads:[~2013-01-03 18:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03  9:30 [Qemu-devel] dataplane build error Gerd Hoffmann
2013-01-03  9:32 ` Stefan Weil
2013-01-03  9:44   ` Stefan Hajnoczi
2013-01-03 18:59     ` Anthony Liguori [this message]

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=87y5ganlcv.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    /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).