[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: executable won't execute



On Sat, May 15, 2010 at 4:15 PM, Sven Joachim <svenjoac@gmx.de> wrote:
> On 2010-05-15 11:04 +0200, Jan C. Nordholz wrote:
>
>>> [readelf output]
>>>
>>> ELF Header:
>>> [...]
>>
>>>  INTERP         0x000114 0x08048114 0x08048114 0x00011 0x00011 R   0x1
>>>      [Requesting program interpreter: /lib/ld-lsb.so.3]
>>
>> That dynamic linker doesn't look right. A little googling shows that
>> Redhat and Suse seem to be using that one now. A missing linker is,
>> by the way, the only other reason for execve() to return ENOENT ("file
>> not found") I know of - missing dependencies produce a different error.
>>
>> Anyway, Debian still has /lib/ld-linux.so.2 - you could try symlinking
>> them, but I doubt it will work.
>
> Why not?  Do you think that Redhat and Suse do something else?  Anyway,
> this symlink should be in the lsb-core package; it was added in 3.0.6
> (see #326609š) but seems to have gone AWOL since then.
>
> Sven
>
>
> š http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326609

So, it's a bug in lsb-core package?

Alexey


Reply to: