From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:53872) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QQedG-0000G3-6N for qemu-devel@nongnu.org; Sun, 29 May 2011 07:58:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QQedF-0004OX-8j for qemu-devel@nongnu.org; Sun, 29 May 2011 07:58:10 -0400 Received: from mail-px0-f174.google.com ([209.85.212.174]:57418) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QQedE-0004OT-VI for qemu-devel@nongnu.org; Sun, 29 May 2011 07:58:09 -0400 Received: by pxi15 with SMTP id 15so1810984pxi.33 for ; Sun, 29 May 2011 04:58:06 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <6331ED7E-D8CF-486E-AD78-13B22783C479@web.de> References: <20110321222037.3067.75336.malonedeb@soybean.canonical.com> <20110328201341.17808.47873.malone@wampee.canonical.com> <6331ED7E-D8CF-486E-AD78-13B22783C479@web.de> Date: Sun, 29 May 2011 12:58:06 +0100 Message-ID: From: Peter Maydell Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [Bug 739785] Re: qemu-i386 user mode on ARMv5 host fails (bash: fork: Invalid argument) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?Q?Andreas_F=C3=A4rber?= Cc: Bug 739785 <739785@bugs.launchpad.net>, qemu-devel@nongnu.org On 29 May 2011 11:19, Andreas F=C3=A4rber wrote: > Am 29.03.2011 um 00:09 schrieb Peter Maydell: >> Short answer: looks like QEMU doesn't currently work on ARMv5 hosts >> (although ARMv7 are fine). I'll look into this if I can manage to >> scare up some suitable hardware. > > I noticed that configure prints any ARM host as "armv4l". As an interim > measure, should we bump that to armv6l if armv5l is known broken? It's only user-mode that doesn't work, I think, so making configure barf on earlier systems would be a little harsh (and that still wouldn't handle the case where you build on one kind of ARM box and then try to run it on an older one). It would probably be easier just to fix the bug than figure out what to do with configure :-) -- PMM