From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59605) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPBIq-0001ld-Cz for qemu-devel@nongnu.org; Sun, 16 Mar 2014 09:40:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPBIl-0004AW-Ke for qemu-devel@nongnu.org; Sun, 16 Mar 2014 09:40:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46215) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPBIl-0004AK-Cp for qemu-devel@nongnu.org; Sun, 16 Mar 2014 09:40:31 -0400 Message-ID: <1394977234.3981.105.camel@localhost.localdomain> From: Marcel Apfelbaum Date: Sun, 16 Mar 2014 15:40:34 +0200 In-Reply-To: References: <5325A5B0.1080102@comstyle.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] QEMU build broken List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: qemu-devel , Andreas =?ISO-8859-1?Q?F=E4rber?= , Brad Smith On Sun, 2014-03-16 at 13:26 +0000, Peter Maydell wrote: > On 16 March 2014 13:22, Brad Smith wrote: > > Commit 0056ae24bc36798fdd96d0b31e217e9f73896736 broke the build of QEMU and > > this affects the 2.0.0 release too. > > > > http://buildbot.b1-systems.de/qemu/builders/default_openbsd_current/builds/700/steps/compile/logs/stdio > > http://buildbot.b1-systems.de/qemu/builders/default_openbsd_4.9/builds/891/steps/compile/logs/stdio > > > > MACHINE and MACHINE_ARCH are used to indicate the meta arch and > > hardware architecture. > > Can we limit the set of system headers we're pulling in to > avoid the header where OpenBSD is defining this? Generally > for specific headers that clash it's nicer to just limit those to > whatever file really needed those defines. I'm assuming it's > not pulled in by one of the POSIX headers... It will be really nice if we could do that, otherwise I need to get creative and find a suitable name for the machine type. By the way, do we have some standard QOM prefixes/suffixes for collisions like this? Thanks, Marcel > > thanks > -- PMM