Checking for libc vs. glibc using Python

[Thomas Gellekum]

"M.-A. Lemburg" <mal at lemburg.com> writes:

> What does the output of ldd look like for glibc and libc on other
> platforms (e.g. Redhat, *BSD, etc.) ?

I forgot (FreeBSD):

/usr/bin/vi:
        libcurses.so.2 => /usr/lib/libcurses.so.2 (0x2809f000)
        libtermcap.so.2 => /usr/lib/libtermcap.so.2 (0x280ab000)
        libc.so.3 => /usr/lib/libc.so.3 (0x280b0000)

but beware of threaded programs:

/usr/local/bin/python:
        libmytinfo.so.2 => /usr/lib/libmytinfo.so.2 (0x280b6000)
        libreadline.so.3 => /usr/lib/libreadline.so.3 (0x280cc000)
        libtermcap.so.2 => /usr/lib/libtermcap.so.2 (0x280ef000)
        libm.so.2 => /usr/lib/libm.so.2 (0x280f4000)
        libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x2810f000)
        libc_r.so.3 => /usr/lib/libc_r.so.3 (0x28124000)

libc_r contains the pthread functions and the corresponding reentrant
libc code.

tg