From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:50781) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvZVt-0003vI-CS for qemu-devel@nongnu.org; Thu, 09 Feb 2012 14:18:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RvZVn-0007iJ-MR for qemu-devel@nongnu.org; Thu, 09 Feb 2012 14:18:36 -0500 Received: from relay1.mentorg.com ([192.94.38.131]:60709) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RvZVn-0007hl-01 for qemu-devel@nongnu.org; Thu, 09 Feb 2012 14:18:31 -0500 From: Paul Brook Date: Thu, 9 Feb 2012 19:18:25 +0000 References: <20120209163708.21062.43255.malonedeb@chaenomeles.canonical.com> <7568D61C-0763-4A4A-9FB0-7F0F60D3C788@suse.de> In-Reply-To: <7568D61C-0763-4A4A-9FB0-7F0F60D3C788@suse.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201202091918.26231.paul@codesourcery.com> Subject: Re: [Qemu-devel] [Bug 929638] Re: qemu 1.0 unable to compile on the pandaboard ES List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Peter Maydell , Alexander Graf , Andreas =?iso-8859-1?q?F=E4rber?= > > On ARM Linux glibc provides a makecontext() that always fails ENOSYS, > > so our configure test thinks there is makecontext support but when we > > try to use it for coroutines it will fail and we abort. > > > > I have a workaround in qemu-linaro that just forces the makecontext > > test to fail on ARM but I don't like that much. It would be better > > to either drop our requirement for makecontext (Paolo had some patches > > to try to do this IIRC) or to handle it failing at runtime. > > Or make the configure test be an execution test and always disable it for > cross-compile? I'd rather not. If at all possible we should avoid runtime tests. Even for "native" systems they generally give the wrong answer as the machine you're building on often isn't the one you will be running on. If we know arm hosts are broken then that's what we should test for in configure (with a comment saying why). IMO consistency between builds for the same target environment is more important than opportunistically probing in a native builds. Paul