Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

when I want to run a program I get the following error:

static:/usr/local/delegate# ./linux64-dg
./linux64-dg: error while loading shared libraries: cannot open shared object file: No such file or directory

Then I check if the lib is existent and it is!!

static:/usr/local/delegate# ldconfig -p | grep (libc6,x86-64) => /lib/

But then ldd shows it could not be loaded:

   static:/usr/local/delegate# ldd linux64-dg
   =>  (0xf7eec000)
   => /lib32/ (0xf7ecb000)
   => /lib32/ (0xf7ec7000)
   => /lib32/ (0xf7ec3000)
   => not found
   => /lib32/ (0xf7eab000)
   => /lib32/ (0xf7d59000)
            /lib/ (0xf7eed000)

What could I do to solve this problem?

(Running ldconfig did not help.)

Thank you very much Jan

share|improve this question
Could you provide the output of "uname -a" and "file /usr/local/delegate/linux64-dg"? The lib32 part seems not right. – touchstone Feb 13 '10 at 8:16
Thanks, problem solved. This was a binary distribution, I now downloaded the source and compiled it myself and everything is working now. (It seems I can't delete questions myself?) – Jan Feb 13 '10 at 8:19
file == /usr/local/delegate/linux64-dg: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, not stripped ## uname -a == Linux static 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64 GNU/Linux – Jan Feb 13 '10 at 8:22
hello touchstone, ohh now I also realilze what the problem is(32vs64 libs). Thank you very much!! You could copy your comment into an answer, then I will give you the tick for the solution. thanks!!!! – Jan Feb 13 '10 at 8:24
up vote 2 down vote accepted

Ok, great it's working now. I think the naming conventions for delegate are somewhat confusing, as seen here:

I guess everyone expects "something64" to be 64bit architecture and not "large file capabilities".

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.