On Fri, Feb 6, 2009 at 9:46 PM, Joshua Hoblitt wrote:
> On Fri, Feb 06, 2009 at 06:44:47PM -0800, James Keenan via RT wrote:
>> On Sun Jan 01 19:09:51 2006, jhobl...@ifa.hawaii.edu wrote:
>> > auto::headers uses the Config module to detect installed header files.
>> > It's ok to get default values
On Fri, Feb 06, 2009 at 06:37:41PM -0800, James Keenan via RT wrote:
> On Wed Dec 14 02:04:12 2005, jhobl...@ifa.hawaii.edu wrote:
> > - The debugging traces could be neater
> >
>
> Are you talking about the Parrot debugger? gdb backtraces?
The w/ glibc stack backtracing that I implimented a co
On Fri, Feb 06, 2009 at 06:44:47PM -0800, James Keenan via RT wrote:
> On Sun Jan 01 19:09:51 2006, jhobl...@ifa.hawaii.edu wrote:
> > auto::headers uses the Config module to detect installed header files.
> > It's ok to get default values and the arch name from Config but it's not
> > OK to depend
On Fri, Feb 06, 2009 at 06:35:05PM -0800, James Keenan via RT wrote:
> On Fri Jan 11 13:17:38 2008, jhobl...@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 deb
