From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: uClibc compatibility or static linking support Date: Sun, 06 Jul 2008 11:02:06 +0300 Message-ID: <48707BFE.4030207@qumranet.com> References: <1215287773.21784.25.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: cristi.magherusan@net.utcluj.ro Return-path: Received: from il.qumranet.com ([212.179.150.194]:52073 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751838AbYGFICI (ORCPT ); Sun, 6 Jul 2008 04:02:08 -0400 In-Reply-To: <1215287773.21784.25.camel@localhost> Sender: kvm-owner@vger.kernel.org List-ID: 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