public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Thorsten Kukuk <kukuk@suse.de>
To: libc-hacker@sources.redhat.com
Subject: Re: Questions about __thread for NSS modules
Date: Wed, 08 Sep 2004 16:38:00 -0000	[thread overview]
Message-ID: <20040908163818.GA15431@suse.de> (raw)
In-Reply-To: <200408261020.i7QAKVE9018030@magilla.sf.frob.com>

On Thu, Aug 26, Roland McGrath wrote:

> > My question is: is this possible at all in NSS modules like libnss_nis.so?
> 
> Sure.  

Ok, I managed now to build a libnss_nis.so.2 module, which uses
thread local storage instead of static variables and locking.

Now my next problem: SuSE and RH have the libc/libpthread with TLS
and NPTL support in /lib/tls and a version without in /lib. But the
path to the libnss_* modules is hardcoded to /lib/libnss_*. So I cannot
copy the libnss_nis module with TLS support into /lib/tls/.

Any ideas how to solve this?

 Thanks,
    Thorsten

-- 
Thorsten Kukuk       http://www.suse.de/~kukuk/        kukuk@suse.de
SuSE Linux AG        Maxfeldstr. 5                 D-90409 Nuernberg
--------------------------------------------------------------------    
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B

  parent reply	other threads:[~2004-09-08 16:38 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
2004-08-26 12:06   ` Thorsten Kukuk
2004-08-30  4:18     ` Roland McGrath
2004-09-08 16:38   ` Thorsten Kukuk [this message]
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=20040908163818.GA15431@suse.de \
    --to=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).