This is the mail archive of the
mailing list for the Cygwin project.
Fwd from daniel_atallah: Re: tcl DLL conflict
- From: Brian Ford <ford at vss dot fsi dot com>
- To: daniel_atallah <daniel_atallah at yahoo dot com>
- Cc: cygwin at cygwin dot com, insight at sources dot redhat dot com
- Date: Fri, 30 Jan 2004 11:05:38 -0600 (CST)
- Subject: Fwd from daniel_atallah: Re: tcl DLL conflict
- References: <712C530350CFD31189E500600891BEC1019457D8@tempus.leanlogistics.com>
- Reply-to: insight at sources dot redhat dot com
Um..., just one. Almost the same as the one here:
> 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.
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
> 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?
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html