From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-devel <kvm@vger.kernel.org>
Cc: Jaswinder Singh Rajput <jaswinder@infradead.org>,
Avi Kivity <avi@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: kvm-userspace build break (linux/types.h)
Date: Thu, 19 Feb 2009 15:50:14 -0600 [thread overview]
Message-ID: <1235080214.16221.26.camel@slate.austin.ibm.com> (raw)
A recent kernel merge breaks kvm-userspace build:
make[1]: Entering directory `/root/hollisb/kvm-userspace.git/libkvm'
gcc -m64 -D__x86_64__ -MMD -MF ./.libkvm.d -g -fomit-frame-pointer -Wall -fno-stack-protector -I /root/hollisb/kvm-userspace.git/kernel/include -c -o libkvm.o libkvm.c
In file included from /usr/include/bits/fcntl.h:24,
from /usr/include/fcntl.h:34,
from libkvm.c:30:
/usr/include/sys/types.h:46: error: conflicting types for ‘loff_t’
/usr/include/linux/types.h:30: error: previous declaration of ‘loff_t’ was here
/usr/include/sys/types.h:62: error: conflicting types for ‘dev_t’
/usr/include/linux/types.h:13: error: previous declaration of ‘dev_t’ was here
[...]
I built like so:
./configure
make -C kernel LINUX=/path/to/kvm.git sync
make
The problem appears to be 00bfddaf7f68a6551319b536f052040c370756b0 and
cef3767852a9b1a7ff4a8dfe0969e2d32eb728df, both from Jaswinder Singh
Rajput <jaswinder@infradead.org>:
-#include <asm/types.h>
+#include <linux/types.h>
With these changes, libkvm.c ends up
including /usr/include/linux/types.h, instead of the
intended ../kernel/include/linux/types.h.
Avi, suggestions? More "make sync" hacks?
--
Hollis Blanchard
IBM Linux Technology Center
next reply other threads:[~2009-02-19 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 21:50 Hollis Blanchard [this message]
2009-02-19 22:03 ` Joerg Roedel
2009-02-20 3:00 ` Zhang, Xiantao
2009-02-20 5:12 ` Jaswinder Singh Rajput
2009-02-20 15:44 ` Hollis Blanchard
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=1235080214.16221.26.camel@slate.austin.ibm.com \
--to=hollisb@us.ibm.com \
--cc=avi@redhat.com \
--cc=jaswinder@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®