If this was REALLY a full tclsh83.exe, I would have less of a problem with it. However, this is some small sub-set of tclsh83 that replaces a FULL cygtclsh80.exe. Perhaps this one should be called cyg-gdb-tclsh. If you have programs like cmake or configure scripts that look for tclsh, they find this one, and mistakenly think it is a working tcl which it is not. The comment in setup.exe says it is only for use with gdb.
-Bill At 08:26 AM 1/28/2003 +0100, S. L. wrote: >[...] >> If that is NOT what you are suggestion -- e.g. that only tclsh83 should >> be renamed -- why? Why is tclsh83 special? >[...] > ><g> >[cough, ough!] >Yes, yes, why?! Why is it the one and only cygwin app (except the specific >applications, e.g. cygcheck, cygpath) that cannot do a "$ /bin/tclsh83.exe >/usr/share/tcl8.3/tcltest1.0/tcltest.tcl" returning a "couldn't read file >"/usr/share/tcl8.3/tcltest1.0/tcltest.tcl": no such file or directory" message ?! >:)) ></g> > >No joke, now, actually it IS special, but this is it. To quote, "any patches >...", 'right ?! :)) > >SLao > >-- >+++ GMX - Mail, Messaging & more http://www.gmx.net +++ >NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
