Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Sun, 25 Jun 2000 22:47:03 -0400
To: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Problem with cygwin-1.1.2 gawk-3.0.4  [Was:  [ANNOUNCEMENT] Updated: gawk-3.0.4]
Message-ID: <20000625224702.B2385@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com
References: <200006251642 DOT MAA01205 AT rtl DOT cygnus DOT com> <004901bfdec8$853dab60$c7a7b5d4 AT p4kpm> <395664C3 DOT CF3A627C AT cygnus DOT com> <000901bfdefc$f079c420$c7a7b5d4 AT p4kpm>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.2i
In-Reply-To: <000901bfdefc$f079c420$c7a7b5d4@p4kpm>; from c.christian.joensson@telia.com on Mon, Jun 26, 2000 at 01:27:33AM +0200

On Mon, Jun 26, 2000 at 01:27:33AM +0200, Christian Jönsson wrote:
>thanks for your reply.  Now, I've clean up a little, :), and attached
>are three tcl script files.  I have "tested" them under Red Hat Linux
>6.2/Intel tcl-8.0.5-35 and the do not generate any parse errors or
>unterminated strings.  They were run as tclsh test{1,2,3}.tcl (tehy did
>not exit but that's an other story.

Sorry.  You still have too many variables.  FYI, tcl/tk are only very
minimally cygwin-aware.  Maybe that's part of your problem.

If cygtclsh80 can't execute awk for some reason, that sort of indicates
a problem with your path.  That would be one thing to check.

Possibly running one of the tools at www.sysinternals.com will show
you what files are being run and may even show you command lines.

Or, you might be able to debug this with gdb.

I guess the bottom line is that I really think that you're going to have
to debug this yourself.

cgf

>Now, trying them under cygwin, with cygtcl gives me this:
>
>BASH.EXE-2.04$ cygtclsh80 test1.tcl
>couldn't execute "awk": no such file or directory
>    while executing
>"exec awk $awkCode"
>    (file "test1.tcl" line 3)
>BASH.EXE-2.04$ cygtclsh80 test2.tcl
>couldn't execute "awk": no such file or directory
>    while executing
>"exec awk $awkCode"
>    (file "test2.tcl" line 3)
>BASH.EXE-2.04$ cygtclsh80 test3.tcl
>couldn't execute "awk": no such file or directory
>    while executing
>"exec awk $awkCode"
>    (file "test3.tcl" line 3)
>BASH.EXE-2.04$

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com