Hello!
 
This is just to let you know what I have found out
regarding the "No such file" error when trying to
execute a certain program.
 
The man pages for execve() states:
 
If  the  executable  is  a  dynamically-linked ELF executable, the interpreter
named in the PT_INTERP segment is used to load the  needed  shared  libraries.
This  interpreter is typically /lib/ld-linux.so.1 for binaries linked with the
Linux libc version 5, or /lib/ld-linux.so.2 for binaries linked with  the  GNU
libc version 2.
 
That is interesting considering /lib/ld-linux.so.1 is nowhere to be found
on the LM8.0 distribution. It is safe to say that this is our missing file:
The Linux loader for programs linked with libc5.
 
Inspection of RH6.2 and LM7.2 boxes shows that they both have the file:
/lib/ld-linux.so.1. Furthermore this file belongs to the ld.so package.
 
Inspection of the rpmfind.net database showed that the ld.so packages are
RH6.2: ld.so-1.9.5-13.i386.rpm
LM7.2: ld.so-1.9.11-4mdk.i386.rpm
 
Now, it turned out that the ld.so-1.9.5-13.i386.rpm package was installed
on the RH7.1 box where my idl_lmgrd was working (it did not produce the
"no such file" error; I do not have a license file on that box).
I am not sure if the ld.so package actually is on the RH7.1 installation
CDs, or if it was left over from an upgrade. At this point I certainly felt
that I was on the right track.
 
Why should I not just install the LM7.2 ld.so package on my LM8.0 box?
This turned out to be quite problematic since ld.so-1.9.11-4mdk.i386.rpm
ALSO contains /sbin/ldconfig which is now found in the ldconfig package
related to the glibc library. I concluded that it was not safe to install
ld.so-1.9.11-4mdk.i386.rpm on LM8.0.
 
The RH ld.so package ld.so-1.9.5-13.i386.rpm does NOT contain /sbin/ldconfig,
so I installed that package instead of the LM ld.so package.
Now my old license manager works again!
 
I have not seen any problems yet, but there just might be some reasons
why Mandrake did not include ld.so in the LM8.0 distribution.
 
 -- Bjarne Thomsen

S/MIME Cryptographic Signature

Reply via email to