comment on

You are aware that you have free access to all of the source code involved, right?

Pick one of the failing tests (like the first one) and run it outside of the "harness" that hides all of the details:

perl -Mblib t/02parse.負 2>&1 | less
[download]

Then, if needed, look at the source code in t/02parse.t and figure out why the particular failing test cases are failing. Then, if needed, look at the source code of the module that gets executed for the test and figure out what is causing the failure. Then, if needed, post questions about what you find to try to solicit help diagnosing.

You can even combine the first 3 steps into one session by using the Perl debugger:

perl -d -Mblib t/02parse.t
[download]

Me looking at t/02parse.t trying to guess what might possibly cause 343 or its 531 subtests to fail sounds likely to be a particularly inefficient way to try to diagnose your problem.

- tye

In reply to Re: Errors building XML::LibXML (source code) by tye
in thread Errors building XML::LibXML by atreyu

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl-Sensitive Sunglasses
	PerlMonks