From: Dunrong Huang <riegamaths@gmail.com>
To: qemu-devel@nongnu.org
Cc: Jorge Bastos <mysql.jorge@decimal.pt>
Subject: Re: [Qemu-devel] [Bug 1008136] [NEW] Cannot compile 1.1.0
Date: Mon, 04 Jun 2012 13:42:03 +0800 [thread overview]
Message-ID: <396bfxas.fsf@gmail.com> (raw)
In-Reply-To: <20120603161453.19379.45755.malonedeb@chaenomeles.canonical.com> (Jorge Bastos's message of "Sun, 03 Jun 2012 16:14:53 -0000")
Jorge Bastos <mysql.jorge@decimal.pt> writes:
> Public bug reported:
>
> Howdy,
>
> Testing QEMU 1.1.0 but doesn't compile:
>
>
> CC fsdev/virtfs-proxy-helper.o
> In file included from /usr/include/i386-linux-gnu/bits/sigcontext.h:28:0,
> from /usr/include/signal.h:339,
> from ./qemu-common.h:38,
> from fsdev/virtfs-proxy-helper.c:23:
> /usr/include/i386-linux-gnu/asm/sigcontext.h:28:2: error: unknown type name '__u64'
> /usr/include/i386-linux-gnu/asm/sigcontext.h:191:2: error: unknown type name '__u64'
> /usr/include/i386-linux-gnu/asm/sigcontext.h:192:2: error: unknown type name '__u64'
> /usr/include/i386-linux-gnu/asm/sigcontext.h:193:2: error: unknown type name '__u64'
> make: *** [fsdev/virtfs-proxy-helper.o] Error 1
>
Check whether you have "int-ll64.h" in your header directory. As i
know, __u64 is defined in int-ll64.h.
Or if you dont want to support virtfs, run ./configure with
"--disable-virtfs" option.
>
> Ideas?
> GCC 4.7, kernel 3.2x
>
> Thanks in advanced,
> Jorge,
>
> ** Affects: qemu
> Importance: Undecided
> Status: New
--
linuxer and emacser and pythoner living in beijing
blog: http://mathslinux.org
twitter: https://twitter.com/mathslinux
google+: https://plus.google.com/118129852578326338750
next prev parent reply other threads:[~2012-06-04 5:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 16:14 [Qemu-devel] [Bug 1008136] [NEW] Cannot compile 1.1.0 Jorge Bastos
2012-06-04 5:42 ` Dunrong Huang [this message]
2012-06-04 5:45 ` [Qemu-devel] [Bug 1008136] " Anthony Liguori
2012-06-04 8:28 ` Jorge Bastos
2012-06-04 8:53 ` Jorge Bastos
2012-06-04 11:56 ` Anthony Liguori
2012-06-04 13:19 ` Jorge Bastos
2012-06-04 19:07 ` Stefan Weil
2012-06-04 20:12 ` Jorge Bastos
2012-07-30 14:37 ` Ken Sharp
2016-10-20 14:07 ` T. Huth
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=396bfxas.fsf@gmail.com \
--to=riegamaths@gmail.com \
--cc=mysql.jorge@decimal.pt \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.