Bad interpreter?

Bad interpreter?

[Shaffer, Kenneth]

If the first line of scripts is #!bash.exe, I get back a bad interpreter
message.

Is there a way that I can get the above line to correctly find bash? I
thought if the full path wasn't specified, that PATH would be used to find
it.

(I've tried copying bash.exe to / and c: and get the same error message.)

Any help greatly appreciated.

--
Ken Shaffer




     - - - - - - -  Appended by Scientific-Atlanta, Inc.  - - - - - - -  
This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Bad interpreter?

[Brian Ford]

On Fri, 7 Nov 2003, Shaffer, Kenneth wrote:

> If the first line of scripts is #!bash.exe, I get back a bad interpreter
> message.
>
Did you try it without the .exe?  I think this works in Cygwin, but is,
AFAIK, unportable.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/