Differences between version 23 and previous revision of CommonErrors.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 23 | Last edited on Friday, July 4, 2003 11:45:46 am | by JohnMcPherson | Revert |
| Older page: | version 22 | Last edited on Thursday, July 3, 2003 3:27:19 pm | by JohnMcPherson | Revert |
@@ -6,14 +6,14 @@
----
!!"No such file or directory"
If you see this message when trying to run a program, even though you can plainly see it right in front of you, there are a couple of possibilities:
-1) Executable is a script
+;
1) Executable is a script:
If it is some kind of script, it might point to an interpreter that doesn't exist on your system. For example, it used to be common to see perl scripts whose first line was:
#!/usr/local/bin/perl
But if you had perl installed as /bin/perl or /usr/bin/perl you would get this message.
-2) Executable is a binary
+;
2) Executable is a binary:
Your dynamic binary executable is linked against a library that doesn't exist, or against a specific dynamic library on your system that has the same name (but different binary interfaces??) as the machine that the file was compiled on. This is particularly annoying as you can also get this message when trying to use ldd(1) to find out which dynamic library is causing the problem! If ldd(1) doesn't work, you are probably missing /lib/ld.so or /lib/ld-linux.so
Sometimes, missing libraries can cause ldd itself to fail, which can make it difficult to determine what the problem is. Eg:
$ ./ninfo
