Mail Archives: cygwin/2003/10/03/13:07:28
The problem ended up being the extention of my script file. It was *.cmd as
it was under my Sun OS. This force the cmd.exe to execute it and never allow
the cygwin environment to take hold.
"Corinna Vinschen" <corinna-cygwin AT cygwin DOT com> wrote in message
news:20031003091604 DOT GD11435 AT cygbert DOT vinschen DOT de...
> On Thu, Oct 02, 2003 at 03:30:28PM -0700, Neil Messmer wrote:
> > 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.
>
>
> Then you're on your own. Check what's going wrong on your machine.
> Regardless of what you're convinced of, it should be a hint that the
> message "'BLA' is not recognized as an internal or external command,..."
> is emitted by cmd.exe but not by any of the Unix shells.
>
> Corinna
>
>
> > > "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/
>
> --
> 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/
- Raw text -