diff options
author | Ulrich Drepper <drepper@redhat.com> | 2000-12-27 03:30:43 +0000 |
---|---|---|
committer | Ulrich Drepper <drepper@redhat.com> | 2000-12-27 03:30:43 +0000 |
commit | be76803a73a6a65929a5f770e694e1116ae419fd (patch) | |
tree | 5091293c69486eac62abfb4a2192e23c05d749a1 /FAQ.in | |
parent | 214414c897e1a3df00a5d91f3eb1aa02bdd1174f (diff) | |
download | glibc-be76803a73a6a65929a5f770e694e1116ae419fd.tar.gz |
Update.
2000-12-11 Bruno Haible <haible@clisp.cons.org>
* Makefile ($(inst_includedir)/gnu/stubs.h): Sort in the C locale.
2000-12-26 Ulrich Drepper <drepper@redhat.com>
* sunrpc/Makefile (rpcgen-cmd): Use single quotes in sed call.
Patch by Ed Connell <Ed.Connell@sas.com>.
Diffstat (limited to 'FAQ.in')
-rw-r--r-- | FAQ.in | 23 |
1 files changed, 23 insertions, 0 deletions
@@ -1560,6 +1560,29 @@ Before doing this look through the list of known problem first: if it cannot directly map a character this is a perfectly good solution since the semantics and appearance of the character does not change. +?? How can I find out which version of glibc I am using in the moment? + +{UD} If you want to find out about the version from the command line simply +run the libc binary. This is probably not possible on all platforms but +where it is simply locate the libc DSO and start it as an application. On +Linux like + + /lib/libc.so.6 + +This will produce all the information you need. + +What always will work is to use the API glibc provides. Compile and run the +following little program to get the version information: + +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +#include <stdio.h> +#include <gnu/libc-version.h> +int main (void) { puts (gnu_get_libc_version ()); return 0; } +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +This interface can also obviously be used to perform tests at runtime if +this should be necessary. + Answers were given by: {UD} Ulrich Drepper, <drepper@cygnus.com> |