From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cristi Magherusan Subject: Re: kvm-87 fails to compile under uClibc Date: Tue, 07 Jul 2009 14:31:30 +0300 Message-ID: <1246966290.32432.24.camel@localhost.localdomain> References: <1246934566.27337.65.camel@localhost.localdomain> <4A53117E.8050305@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-lvXJE9NJOXBp7Us99OxU" Cc: uclibc , kvm To: Avi Kivity Return-path: Received: from bavaria.utcluj.ro ([193.226.5.35]:64327 "EHLO bavaria.utcluj.ro" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754379AbZGGLb7 (ORCPT ); Tue, 7 Jul 2009 07:31:59 -0400 In-Reply-To: <4A53117E.8050305@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: --=-lvXJE9NJOXBp7Us99OxU Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2009-07-07 at 12:12 +0300, Avi Kivity wrote: > 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=3D-lrt" (otherwise the= re > > 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: > > > > =20 >=20 > Well, you need a C library that supports ioperm, or provide it=20 > yourself. If you don't use device assignment an empty function will=20 > suffice. Thanks,=20 I'll try to get it compiled, and as a fallback I could make a stub if everything else fails. > > 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? > > =20 >=20 > Yes. Actually only the headers are 2.6.26.8, the oldest vesion found in buildroot. (I wonder why are older ones being abandoned, since the new ones tend to get bigger and bigger.) The kernel will be 2.6.24 because it's smaller. I know this mismatch may not be good, but I have to get to a compromise. The kernel needs to be as small as possible (everything should fit in a 4MB BIOS flash), and also to support both this version of KVM and OpenVZ at the same time. Older KVM versions have terrible buildsystem issues and I gave up trying to get them compile in buildroot. I think OpenVZ could work on 2.6.26 too, but I haven't tried yet. Could this be a real problem at runtime? Thanks, Cristi. --=20 Ing. Cristi M=C4=83gheru=C8=99an, System/Network Engineer Technical University of Cluj-Napoca, Romania http://cc.utcluj.ro +40264 401247 --=-lvXJE9NJOXBp7Us99OxU Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAkpTMhIACgkQfwrBISYVZFWO+ACeOgvORy/Uu/J6UIhlVHyYfkRv 6/4An39BkBALZYFVLEhWforakeI+761D =zqab -----END PGP SIGNATURE----- --=-lvXJE9NJOXBp7Us99OxU--