All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:02:06 +0300	[thread overview]
Message-ID: <48707BFE.4030207@qumranet.com> (raw)
In-Reply-To: <1215287773.21784.25.camel@localhost>

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.

> Also, it seems that currently there's no way to build it statically
> linked against glibc, so that I can include it in my BIOS image in this
> way. I used the -static CFLAG, but it seems it is still linked
> dinamically against the same libs. Any ideas?
>   

I don't see any reason for that.  Perhaps the build logs will tell.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-07-06  8:02 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 [this message]
2008-07-06 10:07   ` Cristi Magherusan
2008-07-06 14:44     ` 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=48707BFE.4030207@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.