From: Thomas Huth <thuth@redhat.com>
To: Michael Forney <mforney@mforney.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH] osdep.h: Remove <sys/signal.h> include
Date: Wed, 13 Jan 2021 12:44:03 +0100 [thread overview]
Message-ID: <f7d88d49-6108-9035-85e2-b68aff77b316@redhat.com> (raw)
In-Reply-To: <20201027003848.10920-1-mforney@mforney.org>
On 27/10/2020 01.38, Michael Forney wrote:
> Prior to 2a4b472c3c, sys/signal.h was only included on OpenBSD
> (apart from two .c files). The POSIX standard location for this
> header is just <signal.h> and in fact, OpenBSD's signal.h includes
> sys/signal.h itself.
>
> Unconditionally including <sys/signal.h> on musl causes warnings
> for just about every source file:
>
> /usr/include/sys/signal.h:1:2: warning: #warning redirecting incorrect #include <sys/signal.h> to <signal.h> [-Wcpp]
> 1 | #warning redirecting incorrect #include <sys/signal.h> to <signal.h>
> | ^~~~~~~
>
> Since there don't seem to be any platforms which require including
> <sys/signal.h> in addition to <signal.h>, and some platforms like
> Haiku lack it completely, just remove it.
>
> Tested building on OpenBSD after removing this include.
>
> Signed-off-by: Michael Forney <mforney@mforney.org>
> ---
> configure | 10 ----------
> include/qemu/osdep.h | 4 ----
> 2 files changed, 14 deletions(-)
>
> diff --git a/configure b/configure
> index 55e07c82dd..7b57456052 100755
> --- a/configure
> +++ b/configure
> @@ -3095,13 +3095,6 @@ if check_include "libdrm/drm.h" ; then
> have_drm_h=yes
> fi
>
> -#########################################
> -# sys/signal.h check
> -have_sys_signal_h=no
> -if check_include "sys/signal.h" ; then
> - have_sys_signal_h=yes
> -fi
> -
> ##########################################
> # VTE probe
>
> @@ -6182,9 +6175,6 @@ fi
> if test "$have_openpty" = "yes" ; then
> echo "HAVE_OPENPTY=y" >> $config_host_mak
> fi
> -if test "$have_sys_signal_h" = "yes" ; then
> - echo "HAVE_SYS_SIGNAL_H=y" >> $config_host_mak
> -fi
>
> # Work around a system header bug with some kernel/XFS header
> # versions where they both try to define 'struct fsxattr':
> diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
> index f9ec8c84e9..a434382c58 100644
> --- a/include/qemu/osdep.h
> +++ b/include/qemu/osdep.h
> @@ -104,10 +104,6 @@ extern int daemon(int, int);
> #include <setjmp.h>
> #include <signal.h>
>
> -#ifdef HAVE_SYS_SIGNAL_H
> -#include <sys/signal.h>
> -#endif
> -
> #ifndef _WIN32
> #include <sys/wait.h>
> #else
>
Seems like this felt through the cracks, sorry. Since there have been some
changes to the configure scripts, could you please rework your patch and
post again, setting qemu-trivial@nongnu.org into CC: so that it gets more
attention?
Thanks,
Thomas
next prev parent reply other threads:[~2021-01-13 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 0:38 [PATCH] osdep.h: Remove <sys/signal.h> include Michael Forney
2020-10-27 16:30 ` Eric Blake
2021-01-13 11:44 ` Thomas Huth [this message]
2021-01-13 21:56 ` [PATCH v2] " Michael Forney
2021-01-14 6:26 ` Thomas Huth
2021-01-14 22:01 ` John Snow
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=f7d88d49-6108-9035-85e2-b68aff77b316@redhat.com \
--to=thuth@redhat.com \
--cc=mforney@mforney.org \
--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).