David's suggestion will probably work for you. More generally, on
Linux/Unix, you need to specify the full pathname to any executable that is
not in a user's PATH. PATH is an environment variable whose value can be
checked with the command "env" (which prints the entire environment; just
look for PATH).
Usually the PATH does NOT include the current directory (also called the
pwd). (This is different from DOS and often comes as a surprise to
beginners.) Adding ./ before the executable's name tells bash to look for
the program in the pwd.
You CAN change your environment to add the pwd to the PATH, but this is
generally discouraged (especially for the root user) because it creates
security risks.
At 11:42 AM 5/9/99 -0700, David Rysdam wrote:
>try "./program_name" (without the quotes, but with the ./
>
>Ola Theander wrote:
>>
>> I have a problem with some applications that I compiled. The build of the
>> applications goes just fine, but when I'll try to execute them the BASH
>> command shell reports "command not found". If I run the "file" command on
>> the application, file reports "ELF 32-bit LSB executable, Intel 80386,
>> version 1, dynamically linked not stripped".
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.328.4219 voice [EMAIL PROTECTED]
----------------------------------------------------------------
