Why does make echo every command it runs to the screen?
Jason Spiro
jasonspiro4-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Fri Jul 14 10:13:16 UTC 2006
Why does make, by default, echo every command it runs to the screen?
Wouldn't it be better if it did not, and instead gcc echoed the full
pathname of all files that caused errors or warnings while compiling?
Sounds to me such a way would be more in tune with the old Unix
philosophy of commands not displaying any output to the screen unless
there's a problem.
Please CC me,
Jason
--
Jason Spiro: computer consulting with a smile.
I also do computer training and spyware removal for homes and businesses.
Call or email for a FREE 5-minute consultation. Satisfaction guaranteed.
jasonspiro4-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org / 416-781-5938 / Skype ID: jasonspiro
--
The Toronto Linux Users Group. Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
More information about the Legacy
mailing list