This is the mail archive of the
mailing list for the GCC project.
Re: Problems while building with glibc.2.0.6
- To: Ingo Krabbe <ingo at wallace dot ping dot de>
- Subject: Re: Problems while building with glibc.2.0.6
- From: Jim Wilson <wilson at cygnus dot com>
- Date: Tue, 10 Mar 1998 16:49:08 -0800
- cc: egcs-bugs at cygnus dot com
But I get a very strange error while making bootstrap:
Once built for example
the /bin/sh reports 'no such file or directory' when calling this executable
(which seems to be very present while typing 'ls'). I never seen this strange
Why does this happen ?
This can happen if the interpreter for the file is missing. I don't know
exactly how this is indicated in an ELF executable, but it is easy to
demonstrate with a script.
If I put this in a file `tmp.script'
chmod +x tmp.script, and then type tmp.script, I get this (on an Irix6 machine)
tmp.script - Command not found
because the interpreter /foo/bar does not exist. So I'd guess that the
ELF headers are corrupted.