From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: errno, h_errno and _res
Date: Thu, 14 Nov 2002 12:43:00 -0000 [thread overview]
Message-ID: <200211142039.gAEKdtX18199@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Thursday, 14 November 2002 19:01:15 +0100 <20021114190115.H6569@sunsite.ms.mff.cuni.cz>
Unless I missed something, I didn't see any rationale about your moving the
TLS symbols to GLIBC_PRIVATE.
> Shouldn't we change those 3 even in non-TLS builds from errno@@GLIBC_2.0
> to errno@GLIBC_2.0 etc., so that new programs accessing these directly
> simply don't link anymore?
I've done this. But libpthread.so needs to refer to them, so I will have
to do some kind of funny business to make that work.
next prev parent reply other threads:[~2002-11-14 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 10:01 Jakub Jelinek
2002-11-14 10:22 ` Ulrich Drepper
2002-11-14 12:43 ` Roland McGrath [this message]
2002-11-14 12:51 ` Ulrich Drepper
2002-11-14 13:02 ` Roland McGrath
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=200211142039.gAEKdtX18199@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.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).