qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	Bug 1613133 <1613133@bugs.launchpad.net>,
	qemu-devel@nongnu.org
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [Qemu-devel] [Bug 1613133] [NEW] SLIRP code regression fails to build on OpenBSD
Date: Mon, 15 Aug 2016 09:15:20 +0200	[thread overview]
Message-ID: <1656ee88-dda9-2158-c128-9d13e403e1e1@redhat.com> (raw)
In-Reply-To: <596e3698-47dc-949d-0cb5-78864e8d1d8c@redhat.com>



On 15/08/2016 08:53, Thomas Huth wrote:
> On 15.08.2016 02:46, Brad Smith wrote:
>> Public bug reported:
>>
>> The SLIRP code has regressed between 2.6 and 2.7 and now fails to build
>> on OpenBSD.
> [...]
>> In file included from /usr/include/net/if.h:454:0,
>>                  from slirp/slirp.c:34:
>> /usr/include/net/if_arp.h:47:8: error: redefinition of 'struct arphdr'
>>  struct arphdr {
>>         ^
>> In file included from slirp/slirp.c:29:0:
>> slirp/slirp.h:108:8: note: originally defined here
>>  struct arphdr {
>>         ^
> 
> Does it work again if you change the
> 
> #ifndef _WIN32
> #include <net/if.h>
> #endif
> 
> into
> 
> #if !defined(_WIN32) && !defined(__OpenBSD__)
> #include <net/if.h>
> #endif
> 
> at the beginning of slirp/slirp.c ?
> 
> 

Can the struct be renamed to struct slirp_arphdr instead?

Paolo

  reply	other threads:[~2016-08-15  7:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15  0:46 [Qemu-devel] [Bug 1613133] [NEW] SLIRP code regression fails to build on OpenBSD Brad Smith
2016-08-15  6:53 ` Thomas Huth
2016-08-15  7:15   ` Paolo Bonzini [this message]
2016-08-15  8:27     ` Thomas Huth
2016-08-16 10:17 ` [Qemu-devel] [Bug 1613133] " T. Huth
2016-08-16 17:02 ` T. Huth
2016-09-02 20:59 ` T. Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1656ee88-dda9-2158-c128-9d13e403e1e1@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=1613133@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).