From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38516) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPC8X-00036X-Rd for qemu-devel@nongnu.org; Sun, 16 Mar 2014 10:34:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WPC8W-0002V6-Qe for qemu-devel@nongnu.org; Sun, 16 Mar 2014 10:34:01 -0400 Received: from speedy.comstyle.com ([2001:470:1d:8c::2]:48549 helo=mail.comstyle.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WPC8W-0002V0-MO for qemu-devel@nongnu.org; Sun, 16 Mar 2014 10:34:00 -0400 Message-ID: <5325B653.6020105@comstyle.com> Date: Sun, 16 Mar 2014 10:33:55 -0400 From: Brad Smith MIME-Version: 1.0 References: <5325A5B0.1080102@comstyle.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed 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: Marcel Apfelbaum , qemu-devel , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= On 16/03/14 9:26 AM, 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 looks like it is being pulled in via include/qemu/sockets.h which includes netdb.h. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.