Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Chris January" <chris AT atomice DOT net>
To:	"Cygwin AT Cygwin DOT Com" <cygwin AT cygwin DOT com>
Subject:	RE: #! not a recognized internal or external command
Date:	Fri, 3 Oct 2003 09:43:35 +0100
Message-ID:	<ICEBIHGCEJIPLNMBNCMKAEFACNAA.chris@atomice.net>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-MIMEOLE:	Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To:	<bli903$aqv$1@sea.gmane.org>
Importance:	Normal

Did you check the line endings?

> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of Neil Messmer
> Sent: 02 October 2003 23:30
> To: cygwin AT cygwin DOT com
> Subject: Re: #! not a recognized internal or external command
>
>
> I should also mention that the script was executed within a cygwin shell
> window when this error occurred.
> "Neil Messmer" <nmessmer AT octigabay DOT com> wrote in message
> news:bli8s9$ajd$1 AT sea DOT gmane DOT org...
> > I would have thought the paths set in your particuliar environment would
> > have enabled to the find the correct shell for proper execution.
> >
> > I am still convinced it is a setup issue as it works on another machine
> > here. OS versions and hardware are identical.
> >
> > "Corinna Vinschen" <corinna-cygwin AT cygwin DOT com> wrote in message
> > news:20031002204725 DOT GA11435 AT cygbert DOT vinschen DOT de...
> > > On Thu, Oct 02, 2003 at 12:08:25PM -0700, Neil Messmer wrote:
> > > > I have just installed the latest version of cygwin and get the
> following
> > > > error message when running my scripts while running cygwin under Win
> XP.
> > It
> > > > does not matter what shell I specify for the script.
> > > >
> > > > My paths on the win pc is set to /usr/local/bin; /usr/bin; /bin;
> > > > /usr/x11r6/bin.
> > > >
> > > > The simple test script contains one line:
> > > > #! /bin/tsch
> > >
> > > s/tsch/tcsh
> > >
> > > but the *real* problem is that you're trying to start a shell script
> > > under cmd.exe.  That won't work.  The error message is generated by
> > > cmd.exe because it correctly doesn't recognize #! as a command.  The
> > > #! syntax requires support by the starting application, in your case,
> > > by Cygwin.  If the starting application is not a Cygwin shell, you
> > > must start the script as a parameter to the right shell:
> > >
> > > C:\foo> tcsh script-name
> > >
> > > Corinna
> > >
> > > --
> > > Corinna Vinschen                  Please, send mails
> regarding Cygwin to
> > > Cygwin Developer
mailto:cygwin AT cygwin DOT com
> > Red Hat, Inc.
> >
>
>
>
>




--
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/



--
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/

- Raw text -