From: Avi Kivity <avi@qumranet.com>
To: cristi.magherusan@net.utcluj.ro
Cc: kvm@vger.kernel.org
Subject: Re: uClibc compatibility or static linking support
Date: Sun, 06 Jul 2008 17:44:43 +0300 [thread overview]
Message-ID: <4870DA5B.3080402@qumranet.com> (raw)
In-Reply-To: <1215338864.4175.59.camel@localhost>
Cristi Magherusan wrote:
> Hello,
>
> On Sun, 2008-07-06 at 11:02 +0300, Avi Kivity wrote:
>
>> Cristi Magherusan wrote:
>>
>>> Hello,
>>>
>>> As part of my GSoC project I'm working to create a small coreboot
>>> payload containing a KVM-enabled Linux kernel and the KVM tools.
>>>
>>> This involves either compiling and linking KVM against uClibc, or making
>>> a static binary linked against glibc.
>>>
>>> Has anyone tried compiling kvm against uClibc before? I did and it seems
>>> it has some issues. I have fixed some by including aio support inside
>>> uClibc, but it still won't work and I get some linking errors..I can
>>> provide more details if needed.
>>>
>>>
>>>
>> Please post the build log.
>>
>
> Sorry, the part about incompatibility with uClibc was an error on my
> side. It were just my build tools.
> I had some errors in the Makefile I'm using for KVM which are now
> partially fixed and now I got rid of that error, but I have another
> strange one which again seems to be caused by my Makefile.
>
> For building all the stuff I'm using a somehow modified version of
> coreboot's buildrom.
>
> This is my build log:
> http://rafb.net/p/DXMwsg76.html
>
Okay, try to swap the order of the libraries on the command line, or
look at the --start-group and --end-group linker options (you may need
to use the -Wl gcc option with that as well).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-07-06 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 19:56 uClibc compatibility or static linking support Cristi Magherusan
2008-07-06 8:02 ` Avi Kivity
2008-07-06 10:07 ` Cristi Magherusan
2008-07-06 14:44 ` Avi Kivity [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=4870DA5B.3080402@qumranet.com \
--to=avi@qumranet.com \
--cc=cristi.magherusan@net.utcluj.ro \
--cc=kvm@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 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.