[George Peter Staplin]: Sep 2, 2004 - The official Tcl 8.4.x has had the Cygwin build support removed, because it was in need of someone to maintain it, and no one came forward. You can still build Tcl and Tk in [Cygwin] using the [MinGW] packages. To do so you will need to do: export CC="gcc -mno-cygwin"; ./configure --prefix=/some/place/that/won't/conflict && make install You will not be able to use the Cygwin XFree86 server for Tk, unless you patch Tk. Pity. [TV] Maybe this page is informative though, it is possible, I made a windows build of a not so old tcl/tk which I use myself which has an X window interface on top of XP, using cygwin: [Tcl/Tk on Xwindows emulation on XP using Cygwin]. Assuming I can indeed get there maybe a good lecture/workshop subject for the next [Fosdem 2004]. [LES], who is totally ignorant of [C], always wonders and finally picks up the courage to ask '''WHY''' in the world Tcl/Tk have to be made, distributed and compiled with Visual C, a proprietary environment, instead of [GCC], [MingW] and/or other '''free''' environments. [RM] Both tcl and tk 8.4.9 build just fine on cygwin 1.5.12 (hosted by Windows XP Home SP2) using gcc 3.3.3. For tcl, generic/tclClock.c needed a small tweak to make it cope with cygwin's handling of timezone. 25 tests fail (most of them, unicode related) and io.test (io-53.4) hangs (or takes an awful lot of time - I got bored after 15 minutes). Also, I noticed that "make install" tries to create man files with names like "pkg::create.n". Windows doesn't allow colons (and some other "special characters") in file names. I don't think cygwin can go around that. Tk was built with Cygwin XFree86. generic/default.h had to be convinced to use unix/tkUnixDefault.h and not win/tkWinDefault.h "wish" and "widget" run just fine. Great job guys! What was the tweak to tclClock.c so we can replicate it? What steps/commands to make with unix/tkUnixDefault.h and not win/tkWinDefault.h? Thanks in advance. ---- [Category Porting]