All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Hauke Fath <hf@spg.tu-darmstadt.de>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: strsignal(3) mentions sys_siglist, which is gone
Date: Fri, 2 Oct 2020 13:12:19 +0200	[thread overview]
Message-ID: <CAKgNAkjVGqh7BKa3JnKSg6o5fQsqvKg4Om9q1t9uPih4a=BshA@mail.gmail.com> (raw)
In-Reply-To: <20201002103027636420.e5d6e3ba@spg.tu-darmstadt.de>

Hello Hauke,

On Fri, 2 Oct 2020 at 10:28, Hauke Fath <hf@spg.tu-darmstadt.de> wrote:
>
> Hi,
>
> strsignal(3) <https://man7.org/linux/man-pages/man3/strsignal.3.html>
> mentions sys_siglist[], which according to
> <https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=b1ccfc061feee9ce616444ded8e1cd5acf9fa97f>
> has been removed from glibc.
>
> Noted in Arch Linux, see
> <https://lists.archlinux.org/pipermail/arch-general/2020-October/048173.html>.

Thanks. There's actually more problems. Through some accident of
history, sys_siglist was documented in both psignal(3) and
strsignal(3). I've consolidated the discussion to strsignal(3) and
noted that sys_siglist is no longer exported by glibc since v2.32.

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2020-10-02 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02  8:30 strsignal(3) mentions sys_siglist, which is gone Hauke Fath
2020-10-02 11:12 ` Michael Kerrisk (man-pages) [this message]
2020-10-02 13:51   ` Hauke Fath

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='CAKgNAkjVGqh7BKa3JnKSg6o5fQsqvKg4Om9q1t9uPih4a=BshA@mail.gmail.com' \
    --to=mtk.manpages@gmail.com \
    --cc=hf@spg.tu-darmstadt.de \
    --cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.