[Bug libc/21543] sigevent namespace

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=21543

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  9c65eec494676789bc4695561e229ce3ee33be84 (commit)
      from  6257fcfd58479f6b7ae0fdde045b9ff144d543da (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=9c65eec494676789bc4695561e229ce3ee33be84

commit 9c65eec494676789bc4695561e229ce3ee33be84
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Fri Jun 2 19:47:03 2017 +0000

    Fix sigevent namespace (bug 21543).

    signal.h defines the sigevent structure and constants if defined
    __USE_POSIX199309 || defined __USE_XOPEN_EXTENDED.  The
    __USE_XOPEN_EXTENDED condition is incorrect; this structure does not
    appear in XSI standards before Unix98 (which implies
    __USE_POSIX199309).  This patch fixes the conditionals accordingly
    (the existing conditional is correct for siginfo_t, just not for
    sigevent).

    Tested for x86_64.  This does not allow any conform/ XFAILs to be
    removed because of other signal.h namespace bugs.

        [BZ #21543]
        * signal/signal.h: Only include <bits/types/sigevent_t.h> and
        <bits/sigevent-consts.h> if [__USE_POSIX199309], not if
        [__USE_XOPEN_EXTENDED].

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog       |    7 +++++++
 signal/signal.h |    5 ++++-
 2 files changed, 11 insertions(+), 1 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.