"No such file or directory" error when file exists

"No such file or directory" error when file exists

Post by Medora Schau » Wed, 03 Jul 2002 01:06:55



I'm having a problem that sometimes, but not always, happens after I
have built an executable.  When I try to execute it I get an
error of "No such file or directory" even though the executable
is there.  Prepending "./" doesn't help and the file has access
mode of 777.

Most of the time I don't have this problem.  It happened when I
tried to execute a program build with a dynamic link library I
built (something I have never been able to successfully do) and
when I tried to execute the test programs that came with the
gtkextra distribution.

I'm running on a Motorola 5100 with a Linux distribution from
Motorola, kernel 2.4.18-pre7.  It seems to me there must be some
kind of inconsistency in my development environment, possibly
with regards to the linker.

Does anyone know what the problem might be or have ideas on what I
can do to track down the problem?

Thanks in advance.

 
 
 

"No such file or directory" error when file exists

Post by Joost Kremer » Wed, 03 Jul 2002 01:58:49



> I'm having a problem that sometimes, but not always, happens after I
> have built an executable.  When I try to execute it I get an
> error of "No such file or directory" even though the executable
> is there.  Prepending "./" doesn't help and the file has access
> mode of 777.

> Most of the time I don't have this problem.  It happened when I
> tried to execute a program build with a dynamic link library I
> built (something I have never been able to successfully do) and
> when I tried to execute the test programs that came with the
> gtkextra distribution.

> I'm running on a Motorola 5100 with a Linux distribution from
> Motorola, kernel 2.4.18-pre7.  It seems to me there must be some
> kind of inconsistency in my development environment, possibly
> with regards to the linker.

whenever i hear of this problem, it turns out to be the case that the
executable that produces the message is linked against libc whereas
the system uses glibc, or vice versa. even though that is probably not
your problem, there is something wrong with the libraries. what does
ldd tell you?

--
Joost Kremers           http://baserv.uci.kun.nl/~jkremers
Ask 8 slackers how to do something, get 10 answers.
        -- sl in alt.os.linux.slackware