Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <001d01bfdf31$b9bb13a0$c7a7b5d4@p4kpm> From: =?iso-8859-1?Q?Christian_J=F6nsson?= To: 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> <20000625224702 DOT B2385 AT cygnus DOT com> Subject: Re: Problem with cygwin-1.1.2 gawk-3.0.4 [Was: [ANNOUNCEMENT] Updated: gawk-3.0.4] Date: Mon, 26 Jun 2000 07:45:24 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6600 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id BAA07844 ----- Original Message ----- From: "Chris Faylor" Sorry. You still have too many variables. FYI, tcl/tk are only very > minimally cygwin-aware. Maybe that's part of your problem. oh, I see. well, an other trouble here is that I actually would like to be able to run msvc compiled "standard" tcl/tk but that's where the parsing and unterminated string errors occur... :-( > 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. hmm, I have attaced the cygcheck -r -v -s output. But, I really can't understand this being a problem with *my* path. It's BASH.EXE-2.04$ printenv PATH /usr/X11R6/bin:/usr/bin:/USR/LOCAL/BIN:/cygdrive/c/WINDOWS: /cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/COMMAND: /cygdrive/c/PROGRAM/PERL/BIN/:/cygdrive/c/WINDOWS: /cygdrive/c/WINDOWS/COMMAND:. BASH.EXE-2.04$ ls -l /usr/bin/awk.exe lrw-r--r-- 1 chj unknown 19 Jun 25 18:00 /usr/bin/awk.exe -> gawk.exe* BASH.EXE-2.04$ The very trivial test1.tcl script is this: BASH.EXE-2.04$ less test1.tcl set awkCode { { print " "; } } exec awk $awkCode BASH.EXE-2.04$ now, it might be my total lack of tcl script writing and thus a PATH problem, a cygtcl problem with PATH or awk. hmm, perhaps the link awk -> gawk... changing and trying again... BASH.EXE-2.04$ less test1.tcl set awkCode { { print " "; } } exec gawk $awkCode BASH.EXE-2.04$ cygtclsh80.exe test1.tcl gawk.exe: cmd. line:1: { print " gawk.exe: cmd. line:1: ^ unterminated string while executing "exec gawk $awkCode" (file "test1.tcl" line 3) BASH.EXE-2.04$ hmm, there is is, the unterminated string problem, test case 1. (and a discoverg cygtcl "feauture" :), couldn't handle the awk.exe -> gawk.exe link... now, changing test2.tcl and trying again... BASH.EXE-2.04$ less test2.tcl set awkCode { BEGIN { print "\"flow 0" }{ print " "; } } exec gawk $awkCode BASH.EXE-2.04$ cygtclsh80.exe test2.tcl gawk.exe: cmd. line:2: (END OF FILE) gawk.exe: cmd. line:2: parse error while executing "exec gawk $awkCode" (file "test2.tcl" line 3) BASH.EXE-2.04$ same with test3.tcl... BASH.EXE-2.04$ less test3.tcl set awkCode { BEGIN {prev=-1; }{ print " "; } } exec gawk $awkCode BASH.EXE-2.04$ cygtclsh80.exe test3.tcl gawk.exe: cmd. line:1: BEGIN {prev=-1; }{ print " gawk.exe: cmd. line:1: ^ unterminated string while executing "exec gawk $awkCode" (file "test3.tcl" line 3) BASH.EXE-2.04$ A comment, in the fixed font bash, the "^" in unterminated string in the above two cases points at the first " in the print statements. > 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'll wait a little with those... > I guess the bottom line is that I really think that you're going to have > to debug this yourself. well, perhaps someone on the list can shed some light and give me ideas. so far, corinna's encuraged me to pin a problem down, I think I have acheived that somehow. you've made me discover a "feature" of cygtcl, the link-problem. so, bottom line, I've made progress and I really appreciate any kinds of comments. thanks, /ChJ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com