[perl #37934] [TODO] build - log file

James Keenan via RT parrotbug-followup at parrotcode.org
Sat Feb 7 02:35:07 UTC 2009


On Fri Jan 11 13:17:38 2008, jhoblitt at ifa.hawaii.edu wrote:
> A log would be useful if it contained sufficient information to figure
> out why a test passed or failed.  Similar to autoconf's config.log (an
> invaluable debugging tool when tracking down configuration problems).
> 

Is there any reason why this wouldn't suffice:

  perl Configure.pl --test --verbose 2>&1 | tee myconfiglog

For some time now, we've also had Parrot::Configure::Trace, which
enables you to say:

  perl Configure.pl --configure_trace

... and then run methods to extract information about the status of the
Parrot::Configure object as it changes between configuration steps.

If we really need something more than that, we'll have to design and
build it.  If not, let's close this ticket.

Thank you very much.
kid51


More information about the parrot-dev mailing list