From: hjl@lucon.org (H.J. Lu)
To: drepper@cygnus.com
Cc: libc-hacker@cygnus.com
Subject: Re: A patch for linuxthreads
Date: Sun, 25 Oct 1998 08:22:00 -0000 [thread overview]
Message-ID: <m0zXSai-000396C@ocean.lucon.org> (raw)
In-Reply-To: <r2yaq53wwy.fsf@happy.cygnus.com>
>
> hjl@lucon.org (H.J. Lu) writes:
>
> > Sat Oct 24 18:15:53 1998 H.J. Lu <hjl@gnu.org>
> >
> > * linuxthreads/sysdeps/pthread/bits/pthreadtypes.h: Protect
> > with __USE_REENTRANT, __USE_MISC, __USE_GNU and _PTHREAD_H.
> > * linuxthreads/sysdeps/unix/sysv/linux/bits/sigthread.h:
> > Likewise.
>
> This patch is not ok. The changes must be made wherever these files
> get included. I think I did it correctly now. Thanks,
>
I don't think so. The problem is in
sysdeps/unix/sysv/linux/alpha/bits/types.h
sysdeps/unix/sysv/linux/mips/bits/types.h
sysdeps/unix/sysv/linux/sparc/sparc64/bits/types.h
sysdeps/unix/sysv/linux/bits/types.h
signal/signal.h
They include <bits/pthreadtypes.h> or <bits/sigthread.h>. But I didn't
see any changes.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-10-25 8:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-24 18:33 H.J. Lu
1998-10-25 0:59 ` Ulrich Drepper
1998-10-25 8:22 ` H.J. Lu [this message]
1998-10-25 8:22 ` Ulrich Drepper
-- strict thread matches above, loose matches on Subject: below --
2000-09-04 10:48 H . J . Lu
2000-09-04 19:54 ` Ulrich Drepper
1999-12-16 16:12 H . J . Lu
[not found] ` <199912170033.QAA01416@localhost.cygnus.com>
1999-12-16 16:43 ` H . J . Lu
1999-04-14 22:31 H.J. Lu
1999-04-14 23:51 ` Ulrich Drepper
1999-03-17 13:44 Mike Stump
1999-03-18 7:44 ` H.J. Lu
1999-03-16 20:28 H.J. Lu
1999-03-17 2:20 ` Mark Kettenis
1999-03-17 7:21 ` H.J. Lu
1999-03-17 4:52 ` Andrey Slepuhin
1998-12-02 10:35 H.J. Lu
1998-12-02 11:44 ` Ulrich Drepper
1998-08-08 23:26 H.J. Lu
1998-08-09 8:59 ` 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=m0zXSai-000396C@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@cygnus.com \
--cc=libc-hacker@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).