It might be worth thinking about giving varying degrees of the output depending on command line options, or CONFIG directives.
For me - 9/10 times the error tracks back to things like actual C code/XS problems, or some kind of issue arround gcc directives like INC or LIB pathes - maybe there would be a good way of representing this kind of info. Also - it would be still nice to retain the error info that you allready print out, as this shows where it did the build this time. Cheers. On Sun, Oct 06, 2002 at 07:19:10AM -0700, Brian Ingerson wrote: > On 06/10/02 19:13 +1000, Sisyphus wrote: > > Guys, > > > > While improvements to Inline are being discussed, is there any chance of > > having the contents of out.make tee'd to stdout ? > > Yes! This is a great idea. Shouldn't it go to stderr? And are there any other > files that need to get dumped? Any other ideas of what to do here? > > I think this would be one of the lowest hanging fruit. I've just never been > sure of exactly what to do. > > Cheers, Brian
