Hi,
I don't know if this is clear by now, but apparently the glibc version
which is printed is the glibc version used to built python, because
>libcname,libcversion = libc_ver(sys.executable)
in this line the version is determined of sys.executable which is the
python interpreter used to run the script.
But I'm not sure if libc_ver is working correctly, since platform.py
says on my system "with-glibc2.0", but my current version is 2.6.1 and
I doubt that my python 2.5 was built with 2.0.
Some checking:
$ ldd $(which python)
linux-gate.so.1 => (0xb7efb000)
libpython2.5.so.1.0 => /usr/lib/libpython2.5.so.1.0 (0xb7dcf000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb7db7000)
libdl.so.2 => /lib/libdl.so.2 (0xb7db3000)
libutil.so.1 => /lib/libutil.so.1 (0xb7daf000)
libm.so.6 => /lib/libm.so.6 (0xb7d86000)
libc.so.6 => /lib/libc.so.6 (0xb7c34000)
/lib/ld-linux.so.2 (0xb7efc000)
and
$ ls -l /lib/libc.so.6
lrwxrwxrwx 1 root root 13 2008-09-28 01:38 /lib/libc.so.6 -> libc-2.6.1.so
$ qfile /lib/libc.so.6
sys-libs/glibc (/lib/libc.so.6)
$ eix -s glibc
[I] sys-libs/glibc
Available versions: (2.2) [P]2.2.5-r10!s [P]2.3.2-r12!s
[P]2.3.5-r3!s [P]2.3.6-r4!s [P]2.3.6-r5!s 2.4-r4!s 2.5-r2!s 2.5-r3!s
2.5-r4!s **2.5.1!s ~2.6!s 2.6.1!s ~2.7-r2!s ~2.8_p20080602!s
{build crosscompile_opts_headers-only debug erandom gd
glibc-compat20 glibc-omitfp hardened linuxthreads-tls multilib nls
nptl nptlonly pic profile selinux userlocales vanilla}
Installed versions: 2.6.1(2.2)!s(01:38:10 AM
09/28/2008)(glibc-omitfp nls -crosscompile_opts_headers-only -debug
-gd -hardened -multilib -profile -selinux -vanilla)
Homepage: http://www.gnu.org/software/libc/libc.html
Description: GNU libc6 (also called glibc2) C library
As you can see 2.6.1 is installed and python is using this version of glibc.
That's why I'm wondering if it's not libc_ver which is buggy.
Geralt.
