All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Cristi Magherusan <Cristi.Magherusan@net.utcluj.ro>
Cc: uclibc <uclibc@uclibc.org>, kvm <kvm@vger.kernel.org>
Subject: Re: kvm-87 fails to compile under uClibc
Date: Tue, 07 Jul 2009 12:12:30 +0300	[thread overview]
Message-ID: <4A53117E.8050305@redhat.com> (raw)
In-Reply-To: <1246934566.27337.65.camel@localhost.localdomain>

On 07/07/2009 05:42 AM, Cristi Magherusan wrote:
> Hi there,
>
> I'm trying to compile kvm using uClibc instead of glibc.
>
> Besides the fact that kvm needs "--extra-ldflags=-lrt" (otherwise there
> are some missing symbols), there's an error caused by another missing
> symbol that I was unable to fix yet. It's about ioperm, and this is the
> error I get:
>
>    

Well, you need a C library that supports ioperm, or provide it 
yourself.  If you don't use device assignment an empty function will 
suffice.

> I'm using linux-2.6.26.8, uClibc-HEAD(linuxthreds, almost complete
> setup) and gcc 4.3.3.
>
> Also, is this kernel version supposed to work with this kvm?
>    

Yes.


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


  parent reply	other threads:[~2009-07-07  9:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  2:42 kvm-87 fails to compile under uClibc Cristi Magherusan
2009-07-07  3:21 ` Mike Frysinger
2009-07-07  7:34   ` Bernhard Reutner-Fischer
2009-07-07 11:15     ` Cristi Magherusan
2009-07-07 14:33     ` Mike Frysinger
2009-07-07  9:12 ` Avi Kivity [this message]
2009-07-07 11:31   ` Cristi Magherusan
2009-07-07 11:43     ` Avi Kivity
2009-07-08 16:59       ` Cristi Magherusan
2009-07-08 17:07         ` Avi Kivity
2009-07-08 17:34           ` Cristi Magherusan
2009-07-09  8:20             ` Avi Kivity
2009-07-09 17:58               ` Cristi Magherusan
2009-07-07 14:34     ` Mike Frysinger
2009-07-07 15:31     ` Javier Guerra
2009-07-07 15:58       ` Cristi Magherusan
2009-07-08  6:13 ` Natanael Copa
2009-07-08  8:12   ` Cristi Magherusan

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=4A53117E.8050305@redhat.com \
    --to=avi@redhat.com \
    --cc=Cristi.Magherusan@net.utcluj.ro \
    --cc=kvm@vger.kernel.org \
    --cc=uclibc@uclibc.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.