Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

dagolden (6584)

dagolden
  (email not shown publicly)
AOL IM: xdaveg (Add Buddy, Send Message)

Journal of dagolden (6584)

Sunday November 18, 2007
11:21 AM

Can you run Inline::C? I need your help...

[ #34919 ]

If you have or can install Inline::C, I'd greatly appreciate your help testing IO-CaptureOutput-1.05_53.

I've recently adopted IO::CaptureOutput, which is a wonderful tool for capturing program output to STDOUT or STDERR without ties and regardless of whether the output comes from perl, XS or programs in a subprocess.

However, the tests for XS use Inline::C and the C code was found to have portability problems (i.e. segfault on some Win32 platforms). At least one fix for Microsoft Visual C++ (MSVC) then broke on someone else's Linux platform.

(Aside: the fact that it it this hard to portably print the equivalent of "Hello World" to STDOUT and STDERR just astonishes me.)

My latest attempt at updating the C code now uses different code for MSVC and other compilers and now I want to test this as far and as wide as I can.

So if you have installed Inline::C and something that can send test reports (e.g. CPAN::Reporter), please test IO-CaptureOutput-1.05_53. For example, from the CPAN shell:

cpan> test DAGOLDEN/IO-CaptureOutput-1.05_53.tar.gz

Thank you very much,

-- dagolden

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Hi!
    I don't know if you are interested in non-MSVC reports, but this is the test result on Windows Vista, 32bit, with latest Strawberry Perl (mingw/gcc).

    Couldn't seem to install CPAN::Reporter, because IO::CaptureOutput is a dependency...

    Didn't dig into the test failure.
    If you want me to do that, or test something else, just ask.

    ------------------

    Checking if your kit is complete...
    Looks good
    Writing Makefile for IO::CaptureOutput
    cp lib/IO/CaptureOutput.pm blib\lib\IO\CaptureOutput.pm
    cp lib/IO/CaptureOutput.po
    • That's odd. It works for me on Win XP with Strawberry Perl. Maybe it's a Vista thing. Have you customized anything about your installation? (E.g. moved MinGW, not that I think that should matter.)

      Could you please send me the output of "perl -V"? (If you don't mind, please email it to dagolden at cpan.org, so I can followup more conveniently).

      Thanks in advance,

      -- dagolden

    • Has Strawberry Perl been upgraded to use a newer gcc package that supports Vista?
      The last time I checked (2-3 months ago), gcc didn't work on Vista at all, and I couldn't install any perl XS modules.
      I've found something in the mingw mailing lists about a "gcc-vista", but it's not listed on the SF download page.
      (Sorry I can't be more helpful, I don't currently have a Vista box set up).
      • The latest strawberry works and compiles just fine. Installed Inline::C without problems. I had just to add manually the "libexec/blabla/blabla/" path...
        • That's good to know, thanks.
          The lack of a working perl was the last issue stopping me replacing my severely outdated home G4 with a vista box.
          (I don't think linux will ever be family friendly enough)
  • You must have done something right, because with ActivePerl 5.8.8 (build 817) and MinGW 3.2.3 it passes all tests. That is the setup where the module ActivePerl::Config overrides some settings on Config so it can use MinGW gcc as a C compiler.

    So, I'm now trying to run the same tests on Windows 98... I'm expecting some more troubles because Win98 is more primitive in some regards...

    Well indeed. I'm having troubles with it, actually, the same problems when trying to install Inline with CPAN (I ended up instal
    • The final verdict makes sense -- 3 tests are skipped if Inline::C fails to build and bind the source code. (Which happens between test 12 and test 13.) Those nmake problems are from Inline itself. This is a great example of the limitations of PPM's -- you don't get to see any actual tests on your actual system.

      Thanks for running the tests -- I'm glad the ActiveState/MinGW tests worked.

      -- dagolden

  • Running make test
    PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
    t/capture.........ok
    t/capture_exec....ok
    t/noconsole.......ok
    t/wper l ...........skipped
                    all skipped: not MSWin32
    All tests successful, 1 test skipped.
    Files=4, Tests=33, 4 wallclock secs ( 1.39 cusr + 0.42 csys = 1.81 CPU)
        make test -- OK

    FreeBSD qenni.pair.com 6.2-RELEASE-p1 FreeBSD 6.2-RELEASE-p1 #1: Mon Feb 12 2
  • Cygwin: All tests successful.

            osname=cygwin, osvers=1.5.24(0.15642), archname=cygwin-thread-multi-64int
            uname='cygwin_nt-5.1 reini 1.5.24(0.15642) 2007-01-31 10:57 i686 cygwin '

    MSWin32: All tests successful, 3 subtests skipped.

    Set up gcc environment - 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)
    Summary of my perl5 (revision 5 version 8 subversion 8) configuration:
        Platform:
            osname=MSWin32, osvers=5.00, ar