ld, bad logic of dynamic linker search?

[Ivan Popov]

Hello,

my experience is that ld 2.13.2.1 on i386 linux with glibc 2.2.5 / 2.3.2
behaves wrong, in the following situation:

- ld itself is linked against 2.2.5
- I am linking a test binary against glibc 2.3.2 that is located at /somewhere
- I specify -dynamic-linker as /somewhere/ld-2.3.2.so
  (this path gets correctly hardcoded in the resulting binary,
   when I work around the problems below)

but the linker, to resolve remaining references, still is searching for :

1st surprise: "ld-linux.so.2" (why not "/somewhere/ld-2.3.2.so"?)

2nd surprise: searches for it in its LD_LIBRARY_PATH and "standard
              places", hence finds 2.2.5 stuff only, of course
              (and fails to link)

It seems quite illogical. Ld's runtime environment has nothing to
do with my test binary's future runtime environment, and I would be
calling for trouble by putting potentially incompatible stuff in standard
places or ld's LD_LIBRARY_PATH.

My 2c,
--
Ivan