From: hjl@lucon.org (H.J. Lu)
To: kettenis@wins.uva.nl (Mark Kettenis)
Cc: libc-hacker@cygnus.com
Subject: Re: A patch for linuxthreads
Date: Wed, 17 Mar 1999 07:21:00 -0000 [thread overview]
Message-ID: <m10NI8s-000ErMC@ocean.lucon.org> (raw)
In-Reply-To: <199903171030.LAA00153@delius.kettenis.nl>
>
> From: hjl@lucon.org (H.J. Lu)
> Date: Tue, 16 Mar 1999 20:28:23 -0800 (PST)
>
> The patch for Versions fixes another bug.
>
> Which one? HJ, please explain the problem. The __libc_internal
> functions are supposed to be internal, so without an explanation why
> we need to export them I'd say the patch is worng!
>
If you take a look at malloc and linuxthreads, you will find that both
libc and linuxthreads define them and we are expecting "-lpthread"
will replace the ones in libc with the ones in linuxthreads. From
linuxthreads/Versions:
# Internal libc interface to libpthread
__libc_internal_tsd_get; __libc_internal_tsd_set;
what it means libc has to export them so that libpthread can override
them. I hope it is clear now.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1999-03-17 7:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 20:28 H.J. Lu
1999-03-17 2:20 ` Mark Kettenis
1999-03-17 7:21 ` H.J. Lu [this message]
1999-03-17 4:52 ` Andrey Slepuhin
-- 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
1998-12-02 10:35 H.J. Lu
1998-12-02 11:44 ` Ulrich Drepper
1998-10-24 18:33 H.J. Lu
1998-10-25 0:59 ` Ulrich Drepper
1998-10-25 8:22 ` H.J. Lu
1998-10-25 8:22 ` 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=m10NI8s-000ErMC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=kettenis@wins.uva.nl \
--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).