From: Daniel Jacobowitz <dan@debian.org>
To: Florian Lohoff <flo@rfc822.org>
Cc: libc-alpha@sources.redhat.com, Klaus Naumann <spock@mgnet.de>,
Robert Einsle <robert@einsle.de>,
linux-mips@oss.sgi.com
Subject: Re: Probs running ntp on an indy
Date: Thu, 19 Jul 2001 14:20:09 -0700 [thread overview]
Message-ID: <20010719142009.A26517@nevyn.them.org> (raw)
In-Reply-To: <20010719225137.B1599@paradigm.rfc822.org>; from flo@rfc822.org on Thu, Jul 19, 2001 at 10:51:37PM +0200
On Thu, Jul 19, 2001 at 10:51:37PM +0200, Florian Lohoff wrote:
> On Thu, Jul 19, 2001 at 10:24:06PM +0200, Klaus Naumann wrote:
> > I know the problem but no solution. I suspect that it's a
> > problem of the poll function in Big Endian environments, because
> > I can reproduce this on my Indigo2 and on an Ultra 1 as well.
>
> I remember seeing a patch concerning this problem - Something with
> rtsignals - But i cant seem to find it anymore.
That's probably this one. I knew I'd let a patch slip. Glibc folk, is
this OK? The siginfo struct is different on MIPS.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
--- glibc-2.2.3/sysdeps/unix/sysv/linux/mips/bits/siginfo.h.orig Thu May 24 15:35:42 2001
+++ glibc-2.2.3/sysdeps/unix/sysv/linux/mips/bits/siginfo.h Thu May 24 15:35:49 2001
@@ -45,9 +45,9 @@
typedef struct siginfo
{
int si_signo; /* Signal number. */
+ int si_code; /* Signal code. */
int si_errno; /* If non-zero, an errno value associated with
this signal, as defined in <errno.h>. */
- int si_code; /* Signal code. */
union
{
next prev parent reply other threads:[~2001-07-19 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 17:26 Probs running ntp on an indy Robert Einsle
2001-07-19 20:24 ` Klaus Naumann
2001-07-19 20:51 ` Florian Lohoff
2001-07-19 21:20 ` Daniel Jacobowitz [this message]
2001-07-20 6:04 ` Andreas Jaeger
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=20010719142009.A26517@nevyn.them.org \
--to=dan@debian.org \
--cc=flo@rfc822.org \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-mips@oss.sgi.com \
--cc=robert@einsle.de \
--cc=spock@mgnet.de \
/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.