Problems, using libgetcwd.so.0.21

[Simon Josefsson]

Marcus Sundberg <mackan at stacken.kth.se> writes:

> The __getcwd symbol only exists in glibc 2.0, not in libc5 or glibc 2.1.
> If you have a mixed glibc/libc5 system you will get the avove error when
> running libc5 apps.

If I remember correctly, the dynamic linker in Linux check what libc
version (libc5, glibc 2.0 or iBCS) a binary wants and load the correct
one. If this is implemented in some clean way (not likely) perhaps
this could be used to have it decide which libgetcwd should be used,
or something.