in reply to Re^2: How a baisc debugging effort restored my sanity!
in thread How a baisc debugging effort restored my sanity!

all those CPAN reports are bogus and useless - pick any of those:
------------------------------ PROGRAM OUTPUT ------------------------------ Output from '/usr/local/bin/perl5.13.10 Makefile.PL': no display name and no $DISPLAY environment variable while executing "load /usr/lib/libtk8.4.so.0 Tk" ("package ifneeded" script) invoked from within "package require Tk" (file "test-for-tk.tcl" line 1) Your Tcl installation (tclsh) fails to find Tk package.
What use of smoke report without underlying library?

Also, Tcl::Tk, Tkx and Tcl CPAN packages have mailing list where you could have your questions answered.

perl/Tk development is something that is not very inspiring me - Slaven is doing number of efforts and this is certainly deserves much of a respect - but this is mostly wasted efforts, because most of this code is already available in tcl/tk itself.

okay, I think I should take more care of those bogus reports from testers

Replies are listed 'Best First'.
Re^4: How a baisc debugging effort restored my sanity!
by Tux (Canon) on Mar 02, 2011 at 14:47 UTC

    Right, so most smoke reports should skip it. But I know some cpansmokers use fake $DISPLAY's to have modules pass/fail. e.g. see my Tk::Clock based on Tk. (Feel free to steal from Makefile.PL).

    Anyway, I tried to install all modules you mentioned. They all failed because of missing prereq's that are not mentioned in the docs. After I installed the missing tk packages (on OpenSUSE 11.3), I still got:

    $ cpan Tcl::pTk Devel::tcltkdb : : Running make test PERL_DL_NONLAZY=1 /pro/bin/perl "-MExtUtils::Command::MM" "-e" "test_h +arness(0, 'blib/lib', 'blib/arch')" t/*.t t/after.t ..................... ok : t/fileevent.t ................. Can't locate sys/ioctl.ph in @INC (@IN +C contains: /home/merijn/.cpan/build/Tcl-pTk-0.85-MFvlEW/blib/lib /ho +me/merijn/.cpan/build/Tcl-pTk-0.85-MFvlEW/blib/arch /pro/lib/perl5/si +te_perl/5.12.2/i686-linux-64int-ld /pro/lib/perl5/site_perl/5.12.2 /p +ro/lib/perl5/5.12.2/i686-linux-64int-ld /pro/lib/perl5/5.12.2 .) at / +home/merijn/.cpan/build/Tcl-pTk-0.85-MFvlEW/blib/lib/Tcl/pTk/Widget.p +m line 2144. t/fileevent.t ................. Dubious, test returned 2 (wstat 512, 0 +x200) Failed 2/2 subtests t/fileevent2.t ................ Can't locate sys/ioctl.ph in @INC (@IN +C contains: /home/merijn/.cpan/build/Tcl-pTk-0.85-MFvlEW/blib/lib /ho +me/merijn/.cpan/build/Tcl-pTk-0.85-MFvlEW/blib/arch /pro/lib/perl5/si +te_perl/5.12.2/i686-linux-64int-ld /pro/lib/perl5/site_perl/5.12.2 /p +ro/lib/perl5/5.12.2/i686-linux-64int-ld /pro/lib/perl5/5.12.2 .) at / +home/merijn/.cpan/build/Tcl-pTk-0.85-MFvlEW/blib/lib/Tcl/pTk/Widget.p +m line 2144. t/fileevent2.t ................ Dubious, test returned 2 (wstat 512, 0 +x200) Failed 1/1 subtests : Running make test PERL_DL_NONLAZY=1 /pro/bin/perl "-MExtUtils::Command::MM" "-e" "test_h +arness(0, 'blib/lib', 'blib/arch')" t/*.t t/after.t ....... ok : t/text.t ........ can't find package widget::scrolledwindow at /home/m +erijn/.cpan/build/Tcl-Tk-1.04-Mr6h_N/blib/lib/Tcl/Tk.pm line 794. t/text.t ........ Dubious, test returned 2 (wstat 512, 0x200) Failed 3/3 subtests

    But I'm not interested enough to dig any deeper.


    Enjoy, Have FUN! H.Merijn
      given that you have your own modules in perl/Tk, I am not surprised that you do not have interest in digging deeper

      and that is perfectly o-kay,
      you have your code that relies on something, and moving is not easy.

      For me, moving to Tcl::Tk was just a necessary step, because at that time perl/Tk haven't supported Unicode.
      Today, perl/Tk do have Unicode,
      but it will be several steps behind - by design.

      I do not know anything about pTk, I know Tcl::Tk and Tcl CPAN modules.

      Of course your problem could easily be resolved, but given that you do not want it - let it be as it is :)

        But it sounds like you are interested enough. If I can help (you) to improve on these modules, maybe by testing or adding RT tickets to the module queues, I'm all ears.


        Enjoy, Have FUN! H.Merijn