Re^3: Failed building Perl on windows using Visual C++ 2010

how do you figured out what errors o fails?

I keep logs, run the failing tests by hand ( perl harness -v porting/buildtoc.t )

See Re: perl 5.14.0-RC1 is available for testing!

buildtoc is pod generation, the failure of the test doesn't impact generation of perltoc, and that is just a pod file ( list of =head from every pod file)

http://perl5.git.perl.org/perl.git?a=search&h=HEAD&st=free&s=buildtoc.t shows Rename t/porting/buildtoc.t to pod_rules.t, which calls http://perl5.git.perl.org/perl.git/blob/HEAD:/Porting/pod_rules.pl

update: after reviewing Re: perl 5.14.0-RC1 is available for testing! and pod_rules.pl, i don't see that the test actually tests anything of importance

Comment on Re^3: Failed building Perl on windows using Visual C++ 2010 Download Code

Replies are listed 'Best First'.
Re^4: Failed building Perl on windows using Visual C++ 2010 by BAJA (Novice) on Jan 25, 2012 at 06:25 UTC
Nice, thank you Here ends the thread? or do I have to do something to close it as a solved?	[reply]
Re^5: Failed building Perl on windows using Visual C++ 2010 by Anonymous Monk on Jan 25, 2012 at 06:28 UTC
Yup, here it ends, there is no closing, though I've seen some update the root title with `[solved]`, though I don't recall if PerlMonks FAQ endorses the practice	[reply] [d/l]