From: Roland McGrath <roland@redhat.com>
To: Thorsten Kukuk <kukuk@suse.de>
Cc: libc-hacker@sources.redhat.com
Subject: Re: Questions about __thread for NSS modules
Date: Thu, 26 Aug 2004 10:20:00 -0000 [thread overview]
Message-ID: <200408261020.i7QAKVE9018030@magilla.sf.frob.com> (raw)
In-Reply-To: Thorsten Kukuk's message of Thursday, 26 August 2004 11:58:08 +0200 <20040826095808.GA6880@suse.de>
> My question is: is this possible at all in NSS modules like libnss_nis.so?
Sure.
> Do I need to link against libpthread?
No.
> My first try ends in a unresolved "__tls_get_addr" symbol when I try to
> link the module.
I'll assume that's actually ___tls_get_addr if you're on x86.
This suggests your dynamic linker is not built with TLS support.
It defines that symbol.
next prev parent reply other threads:[~2004-08-26 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 9:58 Thorsten Kukuk
2004-08-26 10:20 ` Roland McGrath [this message]
2004-08-26 12:06 ` Thorsten Kukuk
2004-08-30 4:18 ` Roland McGrath
2004-09-08 16:38 ` Thorsten Kukuk
2004-09-08 20:40 ` Roland McGrath
2004-09-09 5:00 ` Thorsten Kukuk
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=200408261020.i7QAKVE9018030@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=kukuk@suse.de \
--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).