From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: compile error
Date: Thu, 10 Jan 2008 11:56:12 +0200 [thread overview]
Message-ID: <4785EBBC.1010408@qumranet.com> (raw)
In-Reply-To: <1199898210.5637.20.camel@basalt>
Hollis Blanchard wrote:
> On Wed, 2008-01-09 at 10:39 +0200, Avi Kivity wrote:
>
>> Zhao, Yunfeng wrote:
>>
>>> Today's tip fails to compile with following error messages:
>>>
>>>
>> [...]
>>
>> Fixed now. Hollis, I had to revert your asm symlink patch to fix this,
>> so we need to find an alternative solution to that problem.
>>
>
> qemu ends up including <asm/byteorder.h> from /usr.
>
> libkvm, on the other hand, ends up including <asm/kvm.h> from the target
> kernel tree.
>
> Since the two components are meaning completely different things when
> referring to the "asm" directory, we should use different include paths.
> The best long-term solution would probably be to remove "-I
> $(KERNELDIR)/include" from libkvm, and instead build against a copy of
> the KVM headers (maybe copied over with that "make sync" target?).
>
> Avi, I think you're responsible for all the build directory munging we
> do currently; what do you think about that?
>
I agree.
The traditional way is to build against installed headers; but we don't
want to do that at this stage. So your suggestion is the closest
thing. But we should make the sync target implicit so users don't have
that additional step.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next prev parent reply other threads:[~2008-01-10 9:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 2:37 compile error Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A029F4E20-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2008-01-09 8:39 ` Avi Kivity
[not found] ` <4784882F.9000103-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-09 17:03 ` Hollis Blanchard
2008-01-10 9:56 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-18 2:38 Zhao, Yunfeng
2008-02-18 10:16 ` Avi Kivity
2008-02-18 13:15 ` Zhao, Yunfeng
2008-02-18 14:51 ` Avi Kivity
2007-07-09 1:13 Compile error Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01B8F5C9-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-09 7:02 ` Avi Kivity
2007-06-28 3:26 debug and breakpoint interrupts handling? Jun Koi
[not found] ` <fdaac4d50706272026r33a09fe5gf96d1e2827e3fa30-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-29 6:12 ` Compile error Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01AE9AD9-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-07-01 9:35 ` Dor Laor
2007-06-01 5:22 compile error Zhao, Yunfeng
[not found] ` <10EA09EFD8728347A513008B6B0DA77A01888A23-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-06-01 6:29 ` Avi Kivity
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=4785EBBC.1010408@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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