Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "daniel_atallah" <daniel_atallah AT yahoo DOT com>
To: <cygwin AT cygwin DOT com>
Subject: tcl DLL conflict
Date: Fri, 30 Jan 2004 11:51:48 -0500
Message-ID: <712C530350CFD31189E500600891BEC1019457D8@tempus.leanlogistics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Many cygwin users who are also users of gaim (http://gaim.sf.net/win32)
have experienced issues lately which have been traced back to the
following:

Cygwin's tcl dll is called tcl84.dll (the same as the native win32
ActiveState tcl dll) and is located in the bin directory. This means
that if cygwin's bin directory is in the path, programs that try to load
the tcl dll will load the cygwin dll instead of the native one (which
obviously causes problems).

I was wondering why the cygwin tcl dll is called tcl84.dll instead of
something like cygtcl84.dll (which seems to be what is done for other
stuff like the perl dll) so that these conflicts don't occur.

Any thoughts?

-Daniel


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