Possible bug in exec with symlink.
Tue Dec 5 16:03:00 GMT 2000
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
echo one.sh running
$ ln -s one.sh two.sh
# An now the bit that does not work.
This script uses the #! like so:
$ head fake_toolchain
# This is a faked up compiler that can
# be used to test the GUI toolchain
Note that it runs just fine from the
But, a symlink to it does not work.
$ ln -s fake_toolchain mygcc
invalid command name "!<symlink>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.
nvalid command name "!<symlink>fake_toolchain "
(file "mygcc" line 1)
Red Hat Inc
Want to unsubscribe from this list?
Send a message to email@example.com
More information about the Cygwin