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: "Dave Korn" <dk AT artimi DOT com>
To: "'Cygwin'" <cygwin AT cygwin DOT com>
Subject: RE: Trouble running awk & deployment of Cygwin
Date: Fri, 14 May 2004 17:47:51 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <5D8C8B50-A5C0-11D8-9314-000A957A7EA8@apple.com>
Message-ID: <NUTMEGIIZS2TRqf69aZ0000010e@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 14 May 2004 16:47:51.0882 (UTC) FILETIME=[32596AA0:01C439D3]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Robert Pollard
> Sent: 14 May 2004 17:04

> The fix on this particular machine was to use gawk instead of awk.
> 
> According to some of the suggestions I received, awk is a symlink to 
> gawk anyway.

  Which, as has been explained, was the underlying cause of the problem.

>  So, this should work fine.  I wonder why I was getting 
> the error since nothing should have changed?

  Apart from the fact that you are now executing an actual executable file,
rather than inadvertently executing an ascii text file.

> Also, contrary to what some believed I wasn't running awk from a DOS 
> prompt.  I was running a bash shell script that was using the 
> command.  

  I think you simply have to be wrong.  There is no question whatsoever that
what has happened is that a file full of ASCII has been invoked as if it
were a 16-bit DOS executable.  Only DOS would do that.  For a start, only
DOS would try to execute a file just because it has '.exe' at the end.

> It worked on my machine but didn't work on another.

  Have you tried comparing the cygcheck output from both of them to look for
differences?  Is it possible the other machine has a duplicate copy of the
executable rather than a symlink?  Let's see the output from "ls -la
/bin/*awk*" on both machines.  Let's see the content of your shell script.
This can't have been happening for just no reason.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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