This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
cygwin bash #! error: bad interpreter
- To: cygwin at cygwin dot com
- Subject: cygwin bash #! error: bad interpreter
- From: Jonathan Hudgins <jhudgins at agames dot com>
- Date: Tue, 06 Nov 2001 08:24:23 -0800
I am creating some scripts and I get the following error:
bad interpreter: no such file or directory
Most machines that have cygwin installed work fine. But one machine reports
this error when I use:
#!bash
OR
#!perl
BUT the error disappears when I use:
#!/usr/bin/perl
#!/usr/bin/bash
And to confuse the matter even more, if I do (on the violating machine):
which perl
OR
which bash
I get:
/usr/bin/perl
OR
/usr/bin/bash
I have reinstalled cygwin several times and looked for anything in the setup or
configuration that might cause such a problem, but I have had no luck.
ALSO suspect: when i do "vi script" from cygwin I see ^M's at the end of lines.
I don't get the same problem on other machines with cygwin. I did remove the ^M
and still had the same problem with my script.
ALSO after seeing an email on this same subject I deleted the regestration keys:
HKEY_CURRENT_USER/Software/Cygnus Solutions
HKEY_LOCAL_MACHINE/Software/Cygnus Solutions
AND then reinstalled.
WHICH STILL DIDN'T work.
Is it possible that I am using a bad setup.exe?
I have reinstalled from a local drive (with packages downloaded in October
2001).
ANY IDEAS?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/