X-Spam-Check-By: sourceware.org Message-ID: <16c33eca0610141951r20fdc9c1y6338a7ae7fc0c54@mail.gmail.com> Date: Sun, 15 Oct 2006 10:51:51 +0800 From: "J. Stevens" To: cygwin AT cygwin DOT com Subject: TcLsh cannot follow symlinks? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I have a feeling that tclsh (TcL shell) in cygwin cannot follow symlinks when using exec or other methods of calling programs. I am using a tclsh script that calls zcat, which is really a symlink to gzip. The script that follows gives "zcat: command not found": #!/bin/tclsh exec zcat test.gz >test.txt #(It cannot follow the symlink?!) But if I get rid of the symlink by changing the name of gzip.exe to zcat.exe and copy it over zcat.exe in /bin, the script unzips test.gz with no problems. #!/bin/tclsh exec zcat test.gz >test.txt #works when I copy gzip.exe binary over zcat.exe symlink On the other hand, the perl script, for example, has no problem with this, so I think it has something to do with TcL. #!/bin/perl print `zcat test.gz >test.txt` #works OK Has anyone encountered this problem? Thanks J. Stevens -- 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/