Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: RE: PerlTk under Cygwin? Date: Fri, 18 Nov 2005 09:23:19 -0600 Message-ID: <297343D29C14AA4D822142893ABEAEF3DCFE7C@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 jAIFRIks002938 Gerrit P. Haase wrote on Friday, November 18, 2005 6:56 AM: > Gerrit P. Haase wrote: > >> Gerrit P. Haase wrote: >>> Christopher Faylor wrote: >>>> On Thu, Nov 17, 2005 at 08:38:26AM -0600, Thrall, Bryan wrote: >>>>> And I'd love to have PerlTk officially packaged :-) >>>> If you're building it OOTB, you're only a couple of steps away from >>>> being a package maintainer. Want to volunteer? Well, since Yaakov beat me to the punch ... :-) >>> Indeed, it builds, not entirely OOTB, there are some include paths >>> missing, I fixed it by copying one header to two other locations, >>> then it works. >> And, besides it builds without errors I cannot run the test, nearly >> all tests are failing for me. Sigh! > > My fix was wrong, the requested header is not to be included and the > build went fine too. With the fix from Yaakov I get only few errors > when running the testsuite. create.t seems to hang. The widget demo > does not act properly, e.g. when running the first demo. > > Yaakov, what are your test results? > > > Gerrit > -- > =^..^= Unfortunately, I'm under time constraints right now, so I won't be able to test PerlTk until about a week from Monday. I'll let you know how it goes then. Thanks for putting this out, Yaakov! -- 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/