Hi Douglas, I'm not sure where it's getting dropped. gcc in particular goes via a perl wrapper, so it could be there. The best thing would be to try to drop back to getting colour output from ltib, then from a .spec file and so on and chase it down that way. Unfortunately I have not time to look at this at the moment.
Regards, Stuart On 09/02/12 17:31, Douglas Peterson wrote: > I recently installed a tool that displays STDERR in red to distinguish > it from STDOUT. Works great, but the reason I did it was to help find > error messages in LTIB spam. It was only after I installed it that I > realized the LTIB shell drops all color output. > > > > Is it possible to restore color to the LTIB shell? > > > > p.s. LTIB itself outputs non-error information to STDERR: > > > > Build path taken because: blah > > + cd blah > > + [ -n ] > > …etc. > > > > While annoying, it would still be helpful if I could get actual compiler > error messages displaying in color. > > > > Douglas > > > > > > _______________________________________________ > LTIB home page: http://ltib.org > > Ltib mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/ltib _______________________________________________ LTIB home page: http://ltib.org Ltib mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/ltib
