This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: Possible bug in exec with symlink.
- To: cygwin at cygwin dot com
- Subject: Re: Possible bug in exec with symlink.
- From: Mo DeJong <mdejong at cygnus dot com>
- Date: Tue, 5 Dec 2000 17:02:15 -0800 (PST)
On Tue, 5 Dec 2000, Christopher Faylor wrote:
> Cygwin sets the argv[0] to be the name of the file which
> invoked the script.
>
> In this case, that's 'mygcc'. 'mygcc' is a symbolic link to a script
> which is running a non-cygwin program. The program is apparently
> looking at argv[0] for some kind of inspiration but is unable to
> decipher cygwin's symlink.
Ahh, yes that is the problem. The Tcl shell is not a Cygwin
app so it does not know how to follow the symlink.
$ ./itcl_sh
% set fd [open ip2k-elf-gcc r]
file204
% read $fd
!<symlink>fake_toolchain
It tries to run "<symlink>fake_toolchain" and puked on that.
> So, I think that Cygwin is behaving appropriately.
>
> cgf
Thanks, I guess I will have to find some other way
to implement this.
Mo DeJong
Red Hat Inc
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com