On Sat, Jul 31, 2010 at 7:19 PM, Peter Lawrence <peterl95...@sbcglobal.net> wrote: > On Jul 31, 2010, at 9:41 AM, Eli Zaretskii wrote: >>> one thing I remember in detail about Sun's make, is that >>> instead of writing a level number >>> >>> make[3]: ... >>> make[2]: ... >>> make[1]: ... >>> >>> it wrote out the directory that the commands had cd'ed to before >>> recursing (and maybe the file name, can't be sure any more) >>> >>> make[foo/bar]: ... >>> make[foo]: ... >>> make[.]: ... >> >> GNU Make displays the equivalent "Entering directory foo..." and >> "Leaving directory foo..." messages. Isn't that the same info? > > the words "Entering" and "Leaving" never appear in the output I captured....
So are you going to read the GNU make info pages to see what conditions make will generate those messages and how something might have suppressed them? Perhaps the gcc maintainers have decided that they hate those messages and have told GNU make to not generate them. If so, complaining to make developers will result in absolutely no progress. You need to figure out who actually has control over the stuff that's bugging you. > typical output from gnu-make when making gcc is such > tossed-salad-scrambled-eggs that nothing is readable, > most lines are hundreds of characters long, as you can > see below the average is over 400 chars/line, here is > some sample output from my failed build, you can't > really tell much of anything from reading this output That problem (monstrously long compile lines) has absolutely nothing to do with make and there's nothing that make can do about it. That's just a problem with the makefile itself and needs to be taken up with the authors of that. Philip Guenther _______________________________________________ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
