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
Message-ID: <20040203152551.47301.qmail@web41511.mail.yahoo.com>
Date: Tue, 3 Feb 2004 07:25:51 -0800 (PST)
From: Daniel Atallah <daniel_atallah AT yahoo DOT com>
Subject: Re: wincvs and cygwin
To: SMore AT empirecorp DOT org, cygwin AT cygwin DOT com, insight AT sources DOT redhat DOT com
In-Reply-To: <6A0F951DBB1DD611A90600805F9F54550282D8E9@mail.empirecorp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

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 AT empirecorp DOT 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


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