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
X-Authentication-Warning:	eos.vss.fsi.com: ford owned process doing -bs
Date:	Fri, 30 Jan 2004 11:05:38 -0600 (CST)
From:	Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender:	ford AT eos
Reply-To:	insight AT sources DOT redhat DOT com
To:	daniel_atallah <daniel_atallah AT yahoo DOT com>
cc:	cygwin AT cygwin DOT com, insight AT sources DOT redhat DOT com
Subject:	Fwd from daniel_atallah: Re: tcl DLL conflict
In-Reply-To:	<712C530350CFD31189E500600891BEC1019457D8@tempus.leanlogistics.com>
Message-ID:	<Pine.GSO.4.58.0401301054580.11773@eos>
References:	<712C530350CFD31189E500600891BEC1019457D8 AT tempus DOT leanlogistics DOT com>
MIME-Version:	1.0
X-IsSubscribed:	yes

Um..., just one.  Almost the same as the one here:

http://www.cygwin.com/ml/cygwin/2004-01/msg01380.html

From:

http://sources.redhat.com/ml/cygwin-announce/2003-02/msg00021.html

> If you have problems with this version of tcltk PLEASE SEND BUG REPORTS
> TO THE INSIGHT MAILING LIST at "insight at sources dot redhat dot com".
> Then the insight maintainers can help rectify these issues.  They are
> familiar with cygwin but, for obvious reasons, should not be forced
> to read the cygwin mailing list to find tcltk/insight problems.
>

Redirecting...

On Fri, 30 Jan 2004, daniel_atallah wrote:

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

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

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

- Raw text -