qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
	Brad Smith <brad@comstyle.com>
Subject: Re: [Qemu-devel] OpenBSD build (was: [PATCH v2] os-posix: Fix build on FreeBSD)
Date: Sun, 6 May 2012 11:05:44 +0000	[thread overview]
Message-ID: <CAAu8pHs3nPOYLpzP7yfH_hKzqOS-HYYWGetMORuh46rvyYBvmA@mail.gmail.com> (raw)
In-Reply-To: <4FA55EAA.3020605@suse.de>

On Sat, May 5, 2012 at 5:08 PM, Andreas Färber <afaerber@suse.de> wrote:
> Am 16.04.2012 09:31, schrieb Gerd Hoffmann:
>> Don't have FreeBSD at hand.  /me has a OpenBSD virtual machine for build
>> tests where this code compiles without issues.
> [snip]
>
> I've now set up an OpenBSD 5.1 VM and it compiles okay. However the
> output is completely chatty due to redundant declarations in the OpenBSD
> system headers.
>
> When I remove -Wredundant-decls from QEMU_CFLAGS it is much better.
>
> Any suggestion how to properly fix this in configure? The QEMU_CFLAGS
> block is before the OS has been checked, and fwiw the flag has been
> around since 2008 (e0e36fe91d2eadcec8159eb6d728c9dd7fc6cf44 / r5931).

Can we have a check whether system headers produce warnings, something
like this:
$ cat headers.c
#include <sys/types.h>
#include <unistd.h>
$ gcc -Wredundant-decls -c headers.c
In file included from headers.c:2:
/usr/include/unistd.h:100: warning: redundant redeclaration of 'lseek'
/usr/include/sys/types.h:210: warning: previous declaration of 'lseek' was here
/usr/include/unistd.h:139: warning: redundant redeclaration of 'ftruncate'
/usr/include/sys/types.h:211: warning: previous declaration of
'ftruncate' was here
/usr/include/unistd.h:164: warning: redundant redeclaration of 'truncate'
/usr/include/sys/types.h:212: warning: previous declaration of
'truncate' was here

>
> Regards,
> Andreas
>
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      reply	other threads:[~2012-05-06 11:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1334412060-1595-1-git-send-email-andreas.faerber@web.de>
     [not found] ` <4F899BBB.1050604@web.de>
     [not found]   ` <4F8BCAC6.7000101@redhat.com>
2012-05-05 17:08     ` [Qemu-devel] OpenBSD build (was: [PATCH v2] os-posix: Fix build on FreeBSD) Andreas Färber
2012-05-06 11:05       ` Blue Swirl [this message]

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=CAAu8pHs3nPOYLpzP7yfH_hKzqOS-HYYWGetMORuh46rvyYBvmA@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=afaerber@suse.de \
    --cc=brad@comstyle.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).