Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
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 17:02:15 -0800 (PST)
From:	Mo DeJong <mdejong AT cygnus DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Possible bug in exec with symlink.
In-Reply-To:	<20001205193715.A16956@redhat.com>
Message-ID:	<Pine.SOL.3.91.1001205165758.26082E-100000@cse.cygnus.com>
MIME-Version:	1.0

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 AT sourceware DOT cygnus DOT com

- Raw text -