Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Guido Guenther <agx@sigxcpu.org>
To: linux-mips@linux-mips.org
Subject: Re: cvs glibc bug?
Date: Tue, 20 May 2003 15:54:42 +0200	[thread overview]
Message-ID: <20030520135441.GI11034@bogon.ms20.nix> (raw)
In-Reply-To: <20030516215147.GT8833@rembrandt.csv.ica.uni-stuttgart.de>

On Fri, May 16, 2003 at 11:51:47PM +0200, Thiemo Seufer wrote:
> SI_TKILL is new in glibc and not yet ported to mips.
Well, the kernel's include/asm-mips/siginfo.h defines SI_KILL as -6
while glibc defines SI_ASYNCNL as -6. Is there a reason for this or is
this just a typo, all other architectures define the later as -60. If
it's a typo i'd like to keep this in sync with other architectures:
 
Index: sysdeps/unix/sysv/linux/mips/bits/siginfo.h
===================================================================
RCS file: /cvs/glibc/libc/sysdeps/unix/sysv/linux/mips/bits/siginfo.h,v
retrieving revision 1.9
diff -u -p -u -r1.9 siginfo.h
--- sysdeps/unix/sysv/linux/mips/bits/siginfo.h	5 Dec 2002 00:23:59 -0000	1.9
+++ sysdeps/unix/sysv/linux/mips/bits/siginfo.h	20 May 2003 12:57:08 -0000
@@ -119,8 +119,10 @@ typedef struct siginfo
    signals.  */
 enum
 {
-  SI_ASYNCNL = -6,		/* Sent by asynch name lookup completion.  */
+  SI_ASYNCNL = -60,		/* Sent by asynch name lookup completion.  */
 # define SI_ASYNCNL	SI_ASYNCNL
+  SI_TKILL = -6,		/* Sent by tkill. */
+# define SI_TKILL	SI_TKILL
   SI_SIGIO,			/* Sent by queued SIGIO. */
 # define SI_SIGIO	SI_SIGIO
   SI_MESGQ,			/* Sent by real time mesq state change.  */

Regards,
 -- Guido

      parent reply	other threads:[~2003-05-20 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 21:33 cvs glibc bug? Benjamin Menküc
2003-05-16 21:51 ` Thiemo Seufer
2003-05-17  8:25   ` Benjamin Menküc
2003-05-20 13:54   ` Guido Guenther [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=20030520135441.GI11034@bogon.ms20.nix \
    --to=agx@sigxcpu.org \
    --cc=linux-mips@linux-mips.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