> Date: Mon, 29 Apr 2013 09:58:50 +0100 > From: Tim Murphy <tnmur...@gmail.com> > Cc: "bug-make@gnu.org" <bug-make@gnu.org> > > try interpreting error messages from compiler/tool X when they're 10 > lines from the file that they refer to and don't include the > filename in the error message.
That's unrelated: interpreting such output will be hard no matter what order it comes in. > b) Demand is usually only going to come from the few anyhow. I think this > is one of those features that few people will know to turn on but many will > benefit anyhow. The reason is that you will start to be able to write > generic make output analysis tools. People who write programs that parse Make output will find and use this switch anyway; we could announce that prominently in NEWS if you think the feature could go unnoticed. But that is irrelevant to interactive human users and their use cases. > c) Lets benchmark it on something like an android build and you can make a > decision after that? Heck, lets try it with various things and be happy it > works. I already tried it, and I'm not happy, FWIW. _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
