in reply to Errors building XML::LibXML

That number of Bad plan errors usually suggests a too old version of Test::More. However, the XML::LibXML test suite doesn't seem to use any of the newer Test::More features, so that seems unlikely.

Running prove -b t/41xinclude.t in the build dir may give you some better clues.

use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name

Replies are listed 'Best First'.
Re^2: Errors building XML::LibXML (bad plan)
by tye (Sage) on Feb 25, 2014 at 15:46 UTC

    No, "bad plan" (for a verified test script) usually just means that the test script died (probably with an informative error message in the process, but prove likes to hide such things from you).

    The error message was likely "segmentation violation", as that is what signal 11 is (at least on one system I checked).

    - tye        

Re^2: Errors building XML::LibXML
by atreyu (Sexton) on Feb 25, 2014 at 17:11 UTC
    Thanks for the suggestion...but it appears that tye has it right on this. In desperation, I tried updating to the latest Test::More (that is, Test::Simple, 1.001002) but I still got the same errors running "make test" on XML::LibXML.