public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: daniel_atallah@yahoo.com
To: insight-gnats@sources.redhat.com
Subject: insight/249: cygwin TCL dll conflict
Date: Thu, 05 Feb 2004 02:53:00 -0000	[thread overview]
Message-ID: <20040205024550.9642.qmail@sources.redhat.com> (raw)


>Number:         249
>Category:       insight
>Synopsis:       cygwin TCL dll conflict
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 05 02:53:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     daniel_atallah@yahoo.com
>Release:        unknown-1.0
>Organization:
>Environment:
cygwin / win32
>Description:
The tcl dll in cygwin is named the same as the native win32 tcl dll (tcl84.dll currently).  This causes programs that probe for tcl to find the cygwin dll instead of the native dll (or no dll at all) if cygwin's bin directory is in the path.  Of course, this causes problems for native win32 programs which cannot load the cygwin dll and subsequently terminate.

This has been happening with the windows port of Gaim (http://gaim.sf.net/win32/) and WinCVS (http://cvsgui.sourceforge.net/).

The argument can obviously be made that the cygwin bin directory should not be in the path, but from the quantity of bugreports coming into the gaim project, it seems to be a common thing to do for users.  

I've been tasked with resolving the problem in gaim, hence my interest in getting this resolved.
>How-To-Repeat:
Install gaim 0.75 on a Windows system with cygwin 1.5.7-1 installed including the tcltk package.

Place cygwin's bin dir in your path.  Start gaim and watch it exit. 
>Fix:
Rename the cygwin tcl dlls to something more consistent with the naming of other cygwin dlls (e.g. cygtcl84.dll, etc)
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2004-02-05  2:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040205024550.9642.qmail@sources.redhat.com \
    --to=daniel_atallah@yahoo.com \
    --cc=insight-gnats@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).