static binaries and NSS

[Thorsten Kukuk]

On Tue, Jun 10, Ulrich Drepper wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Thorsten Kukuk wrote:
> 
> > I think it is time that we add a linker warning to getpwnam and
> > friends, that static linking and using this functions, which calls
> > NSS, is a bad idea.
> 
> That's certainly a good thing to do regardless of any further action.

To avoid adding a link_warning statement in every C file, which
sources nss/getXX*.c, I tried to add it at the end of the
nss/getXX*.c files. But I don't get the expected result. Is it
possible at all with our macros to add a link_warning to this files?
Or do I really have to modify all other files?

  Thorsten

-- 
Thorsten Kukuk       http://www.suse.de/~kukuk/        kukuk@suse.de
SuSE Linux AG        Deutschherrnstr. 15-19        D-90429 Nuernberg
--------------------------------------------------------------------    
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20030611/994a0b6d/attachment.sig>