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 17:44:43 +0300 Message-ID: <4870DA5B.3080402@qumranet.com> References: <1215287773.21784.25.camel@localhost> <48707BFE.4030207@qumranet.com> <1215338864.4175.59.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]:29922 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756817AbYGFOop (ORCPT ); Sun, 6 Jul 2008 10:44:45 -0400 In-Reply-To: <1215338864.4175.59.camel@localhost> Sender: kvm-owner@vger.kernel.org List-ID: 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