This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: static_link_warning

From: "Carlos O'Donell" <carlos at systemhalted dot org>
To: Stanisław Findeisen <stf at eisenbits dot homelinux dot net>
Cc: libc-help at sourceware dot org
Date: Thu, 19 Aug 2010 13:30:11 -0400
Subject: Re: static_link_warning
References: <4C6CD770.9050601@eisenbits.homelinux.net><AANLkTik_AMjSgAu-=27Hkg9ZSqCLWZj7=pOzHx_UH5jD@mail.gmail.com><4C6D5AE0.4040503@eisenbits.homelinux.net>

2010/8/19 StanisÅaw Findeisen <stf@eisenbits.homelinux.net>:
> It's like another copy of glibc being loaded along with those NSS
> modules, right? It could be dynamically loaded but also statically
> linked with that NSS module or with one of the modules it needs?

Yes, the NSS modules and the application each have a copy of glibc.
The applications copy is statically compiled into the binary, and the
NSS modules use the DSO.

No, NSS does not currently support statically linking in a module.
Nobody has done the work to support this.

Cheers,
Carlos.

References:
- static_link_warning
  - From: StanisÅaw Findeisen
- Re: static_link_warning
  - From: Carlos O'Donell
- Re: static_link_warning
  - From: StanisÅaw Findeisen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]