public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
* RE: wincvs and cygwin
@ 2004-02-03 15:47 SMore
  0 siblings, 0 replies; 2+ messages in thread
From: SMore @ 2004-02-03 15:47 UTC (permalink / raw)
  To: daniel_atallah, SMore, cygwin, insight

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: wincvs and cygwin
       [not found] <6A0F951DBB1DD611A90600805F9F54550282D8E9@mail.empirecorp.org>
@ 2004-02-03 15:25 ` Daniel Atallah
  0 siblings, 0 replies; 2+ messages in thread
From: Daniel Atallah @ 2004-02-03 15:25 UTC (permalink / raw)
  To: SMore, cygwin, insight

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-02-03 15:47 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-02-03 15:47 wincvs and cygwin SMore
     [not found] <6A0F951DBB1DD611A90600805F9F54550282D8E9@mail.empirecorp.org>
2004-02-03 15:25 ` Daniel Atallah

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).