From be76803a73a6a65929a5f770e694e1116ae419fd Mon Sep 17 00:00:00 2001 From: Ulrich Drepper Date: Wed, 27 Dec 2000 03:30:43 +0000 Subject: Update. 2000-12-11 Bruno Haible * Makefile ($(inst_includedir)/gnu/stubs.h): Sort in the C locale. 2000-12-26 Ulrich Drepper * sunrpc/Makefile (rpcgen-cmd): Use single quotes in sed call. Patch by Ed Connell . --- FAQ.in | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) (limited to 'FAQ.in') diff --git a/FAQ.in b/FAQ.in index 2daeea9b55..51b7d53a86 100644 --- a/FAQ.in +++ b/FAQ.in @@ -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 +#include +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, -- cgit 1.4.1