On 02 February 2006 17:53, Eric Blake wrote:
>> Because tclsh.exe is a symlink to tclsh84.exe, which has
>>
>> $ ls -l /bin/tclsh.exe
>> lrwxrwxrwx 1 Administrators SYSTEM 11 Jul 30 2004 /bin/tclsh.exe ->
>> tclsh84.exe*
>
> Hmm - we should teach cygcheck to dereference symlinks.
Or at lea
>
> Because tclsh.exe is a symlink to tclsh84.exe, which has
>
> $ ls -l /bin/tclsh.exe
> lrwxrwxrwx 1 Administrators SYSTEM 11 Jul 30 2004 /bin/tclsh.exe ->
> tclsh84.exe*
Hmm - we should teach cygcheck to dereference symlinks.
--
Eric Blake
--
Unsubscribe info: http://cygwin.com/ml/
On 02 February 2006 17:28, Igor Peshansky wrote:
>
> Whatever fix is made, it would be great if cygcheck output the path of
> symlinks it had to chase to get the executable.
There wouldn't be much point doing that without making cygcheck /actually/
chase symlinks first...! ;-)
che
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 +, Eric Blake wrote:
> >> >$ cygcheck tclsh
> >> >Found: C:\cygwin\bin\tclsh.exe
> >> >C:
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 +, Eric Blake wrote:
>> >$ cygcheck tclsh
>> >Found: C:\cygwin\bin\tclsh.exe
>> >C:/cygwin/bin/tclsh.exe
>> >$
>>
>> bash$ ls -l /bin/tclsh*
>
On Thu, 2 Feb 2006, Christopher Faylor wrote:
> On Thu, Feb 02, 2006 at 05:04:42PM +, Eric Blake wrote:
> >$ cygcheck tclsh
> >Found: C:\cygwin\bin\tclsh.exe
> >C:/cygwin/bin/tclsh.exe
> >$
>
> bash$ ls -l /bin/tclsh*
> lrwxrwxrwx 1 cgf None11 Mar 15 2005 /bin/tclsh.exe -> tclsh84.exe
On Thu, Feb 02, 2006 at 05:04:42PM +, Eric Blake wrote:
>$ cygcheck tclsh
>Found: C:\cygwin\bin\tclsh.exe
>C:/cygwin/bin/tclsh.exe
>$
bash$ ls -l /bin/tclsh*
lrwxrwxrwx 1 cgf None11 Mar 15 2005 /bin/tclsh.exe -> tclsh84.exe
-rwxrwxrwx 1 cgf None 16384 Sep 1 2003 /bin/tclsh84.exe
On Thu, 2 Feb 2006, Eric Blake wrote:
> > > 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 progra
On Thu, Feb 02, 2006 at 02:32:08PM +, Steve Smith wrote:
>Thanks for the feedback. So does this mean that it is the tcl that is
>bundled with Cygwin that is broken?
Yes.
>Is there an easy workaround?
PTC?
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem repo
> > 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
On Thu, 2 Feb 2006, Eric Blake wrote:
> Ugh - top-posting reformatted. http://cygwin.com/acronyms/#TOFU
Good point -- I should start including the link to that acronym too... :-)
> > >> When I type "env" the environment appears fine. However, when I
> > >> start a
> > >> tclsh and type
> > >>
When I type "env" the environment appears fine. However, when I
start a
tclsh and type
puts [ exec sh -c "env" ]
the environment is almost empty - this is new behaviour, the whole
environment got fully passed through until recently.
Sounds like YA case of
http://sourceware.org/ml/cygwin/200
Ugh - top-posting reformatted. http://cygwin.com/acronyms/#TOFU
> >> When I type "env" the environment appears fine. However, when I
> >> start a
> >> tclsh and type
> >>
> >> puts [ exec sh -c "env" ]
> >>
> >> the environment is almost empty - this is new behaviour, the whole
> >> environmen
Thanks for the feedback. So does this mean that it is the tcl that is
bundled with Cygwin that is broken?
Is there an easy workaround?
Cheers.
On 2 Feb 2006, at 13:49, Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Steve Smith on 2/2/2006 5:17 AM:
I have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Steve Smith on 2/2/2006 5:17 AM:
>
> I have a similar problem to that reported before under this subject title.
> When I type "env" the environment appears fine. However, when I start a
> tclsh and type
>
> puts [ exec sh -c "env" ]
>
I have a similar problem to that reported before under this subject
title.
When I type "env" the environment appears fine. However, when I start
a tclsh and type
puts [ exec sh -c "env" ]
the environment is almost empty - this is new behaviour, the whole
environment got fully passed thro
On Wed, Sep 28, 2005 at 11:31:28AM -0500, Joey Mukherjee wrote:
>I am having a problem with some Cygwin compiled programs and am hoping
>for some advice. I have a menu program which is started from the
>Desktop by its icon. In this menu program, I modify the environment
>for any child programs
I am having a problem with some Cygwin compiled programs and am hoping
for some advice. I have a menu program which is started from the
Desktop by its icon. In this menu program, I modify the environment
for any child programs that it launches. This works great until the
child program launch
18 matches
Mail list logo
