FW: Exec and parent environment [attn tcltk maintainer]
Dave Korn
dave.korn@artimi.com
Thu Feb 2 17:35:00 GMT 2006
On 02 February 2006 17:32, Igor Peshansky wrote:
> On Thu, 2 Feb 2006, Christopher Faylor wrote:
>
>> On Thu, Feb 02, 2006 at 12:27:53PM -0500, Igor Peshansky wrote:
>>> On Thu, 2 Feb 2006, Christopher Faylor wrote:
>>>
>>>> On Thu, Feb 02, 2006 at 05:04:42PM +0000, Eric Blake wrote:
>>>>> $ cygcheck tclsh
>>>>> Found: C:\cygwin\bin\tclsh.exe
>>>>> C:/cygwin/bin/tclsh.exe
>>>>> $
>>>>
>>>> bash$ ls -l /bin/tclsh*
>>>> lrwxrwxrwx 1 cgf None 11 Mar 15 2005 /bin/tclsh.exe ->
>>>> tclsh84.exe -rwxrwxrwx 1 cgf None 16384 Sep 1 2003 /bin/tclsh84.exe
>>>> bash$ cygcheck /bin/tclsh84.exe
>>>> d:/cygwin/bin/tclsh84.exe
>>>> L:\WINXP\system32\KERNEL32.dll
>>>> L:\WINXP\system32\ntdll.dll
>>>> d:/cygwin/bin\cygwin1.dll
>>>> L:\WINXP\system32\ADVAPI32.DLL
>>>> L:\WINXP\system32\RPCRT4.dll
>>>> d:/cygwin/bin\tcl84.dll
>>>> L:\WINXP\system32\USER32.dll
>>>> L:\WINXP\system32\GDI32.dll
>>>>
>>>> I will look into fixing this.
>>>
>>> Whatever fix is made, it would be great if cygcheck output the path
>>> of symlinks it had to chase to get the executable. Also, outputting
>>> "Not an executable" for scripts and such would help.
>>
>> I will not look into fixing this.
>
> I will look into fixing this.
> Igor
Does that mean you plan to apply a patch to cgf so that he _will_ look into fixing it?
cheers,
DaveK
--
Can't think of a witty .sigline today....
More information about the Cygwin-talk
mailing list