This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
RE: wincvs and cygwin
- From: SMore at empirecorp dot org
- To: daniel_atallah at yahoo dot com, SMore at empirecorp dot org, cygwin at cygwin dot com, insight at sources dot redhat dot com
- Date: Tue, 3 Feb 2004 10:47:31 -0500
- Subject: RE: wincvs and cygwin
Un-installing cygwin's tcl/tk now allows my wincvs to work once again.
Thanks for your help.
-Steve More
-----Original Message-----
From: Daniel Atallah [mailto:daniel_atallah@yahoo.com]
Sent: Tuesday, February 03, 2004 10:26 AM
To: SMore@empirecorp.org; cygwin@cygwin.com; insight@sources.redhat.com
Subject: Re: wincvs and cygwin
I believe that this is related to the problem that i
have with gaim.
If the tcl dll included with cygwin conflicts with the
native win32 tcl (still a problem if you don't have
native tcl installed)
When wincvs tries to start up, it probes for a tcl
dll, and when it finds it it tries to load it. If it
is the cygwin tcl dll, it will cause the program to
exit.
>From what i can tell, the best way to solve this would
be for the cygwin tcl dlls to be named differently,
e.g. "cygtcl84.dll" instead of "tcl84.dll" (this is
what is done for perl and others).
>From what i understand, the Insight crew maintain the
cygwin tcl, so i have posted this message to their
list as well.
-D
--- SMore@empirecorp.org wrote:
> I have upgraded to cygwin 1.5.7 and can no longer
> execute wincvs in a cygwin
> bash shell.
>
> After I execute the command: wincvs
>
> The wincvs windows start to appear then it just
> exits.....
>
> $ echo $?
> 128
>
>
> -Stephen More