From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?T3phbiDDh2HEn2xheWFu?= Subject: Re: Build failure with qemu-kvm 0.1x Date: Sat, 09 Jan 2010 01:51:52 +0200 Message-ID: <4B47C518.9060806@pardus.org.tr> References: <4B47C095.8090304@pardus.org.tr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE To: KVM list Return-path: Received: from lider.pardus.org.tr ([193.140.100.216]:44111 "EHLO lider.pardus.org.tr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754253Ab0AHXvw (ORCPT ); Fri, 8 Jan 2010 18:51:52 -0500 Received: from [192.168.1.2] (unknown [88.249.178.198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: ozan) by lider.pardus.org.tr (Postfix) with ESMTPSA id 82A80A7AB55 for ; Sat, 9 Jan 2010 01:43:45 +0200 (EET) In-Reply-To: <4B47C095.8090304@pardus.org.tr> Sender: kvm-owner@vger.kernel.org List-ID: Ozan =C3=87a=C4=9Flayan wrote: > Hi, > > > and so on.. I suspect some locale specific things going on with i386 = and > TARGET_I386 as i->I conversion is a little bit problematic in Turkish > collation. That's why I experimented a bit with LC_ALL=3DC but didn't > figure out anything useful. > =20 And yes that was it: target_arch_name=3D"`echo $TARGET_ARCH | tr '[:lower:]' '[:upper:]'`" this can't convert i386 to I386 which then appears in #ifdef TARGET_I386. This will probably only affect languages in which CAPITAL(i) =3D =C4=B0 CAPITAL(=C4=B1) =3D I e.g. Turkish. I work-arounded it by exporting LC_ALL=3DC at the beginning of the configure script. It's on yours now to decide to fix it in upstream or = not, Thanks anyway :) Regards,