Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: RE: PerlTk under Cygwin? Date: Thu, 17 Nov 2005 08:38:26 -0600 Message-ID: <297343D29C14AA4D822142893ABEAEF3DCFC29@srv1163ex1.flightsafety.com> From: "Thrall, Bryan" To: "Cygwin List" X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id jAHEccVT006788 Yaakov S (Cygwin Ports) wrote on Wednesday, November 16, 2005 5:44 PM: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Bruce Dobrin wrote: >> Well, obsolete or not, the tk800.025 for win32 from sourceforge is >> building and working on 1.5.18 with it's perl5.8.5. Any chance a >> non-obsolete version for win32 anytime? We use this native a lot. > > 804.x doesn't build for Win32, and as X11 was working with only a > minor patch and I didn't care either way, I decided to stop > supporting Win32. You could take the source tarball from there and > try recompiling with the current perl and see how that works for you. > > > Yaakov > Cygwin Ports I'm curious about the patch you mention, since I maintain an internal PerlTk Cygwin package for my company, and I haven't had any problems OOTB (the last version I built was 804.027 against perl 5.8.7). And I'd love to have PerlTk officially packaged :-) -- Bryan Thrall FlightSafety International Bryan.Thrall@flightsafety.com -- 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/