Follow-up Comment #1, bug #67804 (group make): These lines actually serve an important purpose: they allow tools that track the output of the build to know where in the filesystem the build is running, so that source files etc. can be properly located. If we suppress them then this will break.
I don't really see how this can work since you can't know, when you print the
previous "leaving directory", that the next "entering directory" will be the
same.
I guess you'd have to always buffer the next line and not print it out until
you were ready to print the line after it, and if the next line was "leaving"
and the line after was "entering" you'd omit both of them, but if the line
after was something else you'd print the next line.
To me this seems like the wrong solution.
The right solution is to fix this build system so it doesn't do this! It's
ridiculous that the build system is invoking an entirely new invocation of
make, with all that implies about parsing makefiles, managing variables, etc
etc. just to build one object file then exiting, then started an entirely new
make just to build the next object file, etc.
If this makefile was written in a coherent and sane way, then one invocation
of make (and one entering/leaving) would build all the object files in that
directory.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67804>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
