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

Will Coleda via RT parrotbug-followup at parrotcode.org
Thu Nov 5 05:43:40 UTC 2009


On Sat Feb 07 02:39:21 2009, jhoblitt at ifa.hawaii.edu wrote:
> On Fri, Feb 06, 2009 at 06:35:05PM -0800, James Keenan via RT wrote:
> > 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
> 
> Even that would be helpful but do you really want to document that for
> every possible shell that a user might be using and then have to point
> people at that document constantly?  In my expirence it's nice to be
> able to just ask people to attach config.log from the build dir.
> 
> > 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.
> 
> That's exactly the sort of verbosity that you want to go into a log
> file.
> 
> -J
> 
> --
> 

Now being tracked at https://trac.parrot.org/parrot/ticket/1199; followup discussion there.

Regards.

-- 
Will "Coke" Coleda


More information about the parrot-dev mailing list