From: ericblake AT comcast DOT net (Eric Blake)
To: cygwin AT cygwin DOT com
Subject: Re: Exec and parent environment [attn tcltk maintainer]
Date: Thu, 02 Feb 2006 17:04:42 +0000
Message-Id: <020220061704.21728.43E23BAA00009920000054E022092246270A050E040D0C079D0A@comcast.net>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

> > But if cygexec mounting is turned on, then a native windows program in
> > that mount point will be mistakenly treated as a cygwin program, such
> > that cygwin tries to use only the cygwin method for passing the
> > environment to the child program.  My guess is that you are calling
> > tclsh from a cygwin shell (bash?), and that cygwin is assuming the child
> > (tclsh) can understand cygwin's environment because it lives in /bin,
> > even though it is a windows native executable and needs the windows
> > environment.
> 
> Well, tclsh is a *Cygwin* executable that uses native Windows calls
> (CreateProcess) under the covers (in tcl84.dll).  I'm not sure if it would
> even help to be able to mount it as a "non-cygwin executable"...  CGF?

Really?

$ cygcheck tclsh
Found: C:\cygwin\bin\tclsh.exe
C:/cygwin/bin/tclsh.exe
$

My understanding of the cygexec magic was that if it was
determined that an .exe had a startup dependency on
cygwin1.dll, but tclsh has NO dll dependencies at startup
(any dlls are pulled in with dynamic loads during execution),
so how would cygwin1.dll be able to think that tclsh is
a cygwin executable?

--
Eric Blake

--
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/