Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

I am very new to perl. I am trying to install perl in ARM sytem which runs on NetBSD5.1 OS.

I have run "make" after "configure". On running "make test", I got the below error. 
dist/ExtUtils-ParseXS/t/001-basic ............................. pid 15
+174 (perl), uid 0: exited on signal 4 (core not dumped, err = 2)
FAILED--expected 17 tests, saw 7 <br>

dist/ExtUtils-ParseXS/t/002-more .............................. pid 69
+10 (perl), uid 0: exited on signal 4 (core not dumped, err = 2)
FAILED--expected 29 tests, saw 6 <br>

dist/ExtUtils-ParseXS/t/003-usage ............................. pid 14
+096 (perl), uid 0: exited on signal 4 (core not dumped, err = 2)
FAILED--expected 24 tests, saw 6 <br> 

dist/ExtUtils-ParseXS/t/101-standard_typemap_locations ........ ok

dist/ExtUtils-ParseXS/t/102-trim_whitespace ................... ok
dist/ExtUtils-ParseXS/t/103-tidy_type ......................... ok
dist/ExtUtils-ParseXS/t/104-map_type .......................... ok
dist/ExtUtils-ParseXS/t/105-valid_proto_string ................ ok
dist/ExtUtils-ParseXS/t/106-process_typemaps .................. ok
dist/ExtUtils-ParseXS/t/108-map_type .......................... ok
dist/ExtUtils-ParseXS/t/109-standard_XS_defs .................. ok
dist/ExtUtils-ParseXS/t/110-assign_func_args .................. ok
dist/ExtUtils-ParseXS/t/111-analyze_preprocessor_statements ... ok
dist/ExtUtils-ParseXS/t/112-set_cond .......................... ok
dist/ExtUtils-ParseXS/t/113-check_cond_preproc_statements ..... ok
dist/ExtUtils-ParseXS/t/114-blurt_death_Warn .................. ok
dist/ExtUtils-ParseXS/t/115-avoid-noise ....................... ok
dist/ExtUtils-ParseXS/t/501-t-compile ......................... ok
dist/ExtUtils-ParseXS/t/510-t-bare ............................ ok
dist/ExtUtils-ParseXS/t/511-t-whitespace ...................... ok
dist/ExtUtils-ParseXS/t/512-t-file ............................ ok
dist/ExtUtils-ParseXS/t/513-t-merge ........................... ok
dist/ExtUtils-ParseXS/t/514-t-embed ........................... ok
dist/ExtUtils-ParseXS/t/515-t-cmd ............................. ok
dist/ExtUtils-ParseXS/t/516-t-clone ........................... ok
dist/ExtUtils-ParseXS/t/517-t-targetable ...................... ok
dist/ExtUtils-ParseXS/t/600-t-compat .......................... ok

[download]
Could someone please help on this? How can I proceed with this? Please help

Replies are listed 'Best First'.
Re: Perl-5.22.1 in ARM system
by Anonymous Monk on Dec 31, 2015 at 07:05 UTC

    someone please help on this? How can I proceed with this? Please help

    Your options are

    Ignore it, go ahead and install

    Go back a version

    Something else :)

[reply]
      :) Thanks for the reply. I am wondering/worried if this failure cause any more issue?
[reply]
        I am wondering/worried if this failure cause any more issue?

        You should send an email to perlbug at perl dot org.

        Include the test results that you provided in your first post, and also provide the output of perl -V for the offending perl.
        That is, in the directory in which you built perl by running 'make', run ./perl -I./lib -V (though the "-I./lib" is perhaps not needed).
        That should spit out all of the configuration information that they'll want to see.

        In the meantime, *I* would install the perl you've built and see how it goes - you can always overwrite it (or remove it).
        ExtUtils::ParseXS has effect only during the building of a perl extension (ie a module that has a C component that needs to be compiled).
        In the usual course of running perl scripts, a problem with ExtUtils::ParseXS is not something that's going to jump up and bite you.
        If those failures do bite, it will be when you're building a perl extension - in which case the extension might fail to build, or might fail to pass its test suite.
        No guarantees, of course ;-)

        Cheers,
        Rob
[reply]
[d/l]
[select]

        :) Thanks for the reply. I am wondering/worried if this failure cause any more issue?

        Issues with what?

        No, your computer will not explode if a test fails

        Its like you're assembling a bicycle, and you're missing a sticker/decal... -- explosion is imminent

        There are 2 to 3 thousand test files ... and each does many tests ... so how many failed out of how many?

[reply]

Back to Seekers of Perl Wisdom