bug-glibc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: static linking with getgrgid follow up


From: David Stuart
Subject: Re: static linking with getgrgid follow up
Date: Wed, 02 Oct 2002 17:24:52 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020605

Is there any way to discover which version of glibc a binary was statically linked against? Will nm do that?

You'd think that the redhat update program would take care of all of these things for me.. (also it would be nice if there was a dependency to the correct glibc version??)

It does seem to me that my problems began after updating some packages. If I could identify what, exactly, it would be helpful.

Geoff Keating wrote:

I think it might help if you knew that when a program that uses NSS
(also, I think, iconv) is linked statically to glibc, it can still use
dynamic libraries, basically everything of the form /lib/libnss*.so.
Making these work is complicated and is guaranteed to work only if the
executable was linked with the very same version of glibc that is
installed, which is why we recommend that people do not link
executables statically if they use NSS functions.

Unfortunately, many people think that static linking will give them a
portability or security benefit, usually based on how some really old
OS behaved.  Actually, static executables are less portable (see
above) and less secure (because security problems can't be
fixed by just installing new shared libraries).







reply via email to

[Prev in Thread] Current Thread [Next in Thread]