On Tue Jan 22 14:02:30 2008, ajr wrote: > > Any suggestions for further floundering would be welcome. >
Well, here's one thought. You could try running Configure.pl with the addition of the --configure_trace option. Read the POD for Parrot::Configure::Trace to see how you would then be able to trace the evolution of specific values inside the Parrot::Configure object as you go through the 60+ config steps. Caveat: Every time I've used P::C::Trace, it's been on a configuration that completed successfully and hence resulted in a well-formed trace file at the end of configuration. Don't know how it will work if you get a failure *during* configuration as opposed to during 'make'.
