From: Joel Klecker <jk@espy.org>
To: libc-hacker@sourceware.cygnus.com
Subject: Current glibc-2-1-branch linuxthreads/signals.c doesn't compile
Date: Fri, 22 Oct 1999 00:10:00 -0000 [thread overview]
Message-ID: <v0420550ab435b947f3a6@[206.163.71.146]> (raw)
Without --with-headers, <ucontext.h> ends up being gotten from the system
headers, which is perhaps why this wasn't caught before.
linuxthreads/signals.c doesn't appear to need any of the functions prototyped in
<ucontext.h>, so I believe this is the correct fix.
1999-10-22 Joel Klecker <espy@debian.org>
* signals.c: Include <sys/ucontext.h> instead of <ucontext.h>.
Index: linuxthreads/signals.c
===================================================================
RCS file: /cvs/glibc/libc/linuxthreads/signals.c,v
retrieving revision 1.8.2.3
diff -u -r1.8.2.3 signals.c
--- linuxthreads/signals.c 1999/09/25 16:59:50 1.8.2.3
+++ linuxthreads/signals.c 1999/10/22 06:54:36
@@ -19,7 +19,7 @@
#include "pthread.h"
#include "internals.h"
#include "spinlock.h"
-#include <ucontext.h>
+#include <sys/ucontext.h>
#include <sigcontextinfo.h>
int pthread_sigmask(int how, const sigset_t * newmask, sigset_t * oldmask)
--
Joel Klecker (aka Espy) <URL: mailto:espy@debian.org >
Debian Package Maintainer for the GNU C Library.
next reply other threads:[~1999-10-22 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-22 0:10 Joel Klecker [this message]
1999-10-23 21:05 ` Ulrich Drepper
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='v0420550ab435b947f3a6@[206.163.71.146]' \
--to=jk@espy.org \
--cc=libc-hacker@sourceware.cygnus.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).