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 sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Tue, 5 Dec 2000 16:03:44 -0800 (PST) From: Mo DeJong To: cygwin AT cygwin DOT com Subject: Possible bug in exec with symlink. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi all. I think I have run into a bug in the way Cygwin deals with symlinks in an exec. I am using the most recent net release on an NT box. First, the simple case that works correctly. $ cat one.sh #!/bin/sh echo one.sh running sleep 5 exit 0 $ ./one.sh one.sh running $ ln -s one.sh two.sh $ ./two.sh one.sh running # An now the bit that does not work. This script uses the #! like so: $ head fake_toolchain #! /home/mdejong/install/SN452/bin/itcl_sh # This is a faked up compiler that can # be used to test the GUI toolchain Note that it runs just fine from the cmd line. $ ./fake_toolchain fake_toolcahin script But, a symlink to it does not work. $ ln -s fake_toolchain mygcc $ ./mygcc invalid command name "!fake_toolchain " while executing "!fake_toolchain " (file "./mygcc" line 1) It looks like Cygwin is getting confused about which file it should pass to the program. It is looking for the #! in the symlink but when it gets run, it passes the name of the symlink on the cmd line. ./itcl_sh.exe mygcc nvalid command name "!fake_toolchain " while executing !fake_toolchain " (file "mygcc" line 1) cheers Mo DeJong Red Hat Inc -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com