Re: always echoing commands (patch)

[Johan Bezem]

I've been using an environment variable for that for ages. Some of the
command lines are too simple (like a 'cp' or 'mv') and get their '@'-sign
directly; compiler and linker commands get their $(MY_AT) at the position
where the @-sign should be. Normally I have an "export MY_AT=@" (using bash)
in my profile, but if I set it to the empty string, all relevant commands
are echoed.

FWIW,

Johan Bezem
CSK Software AG

Marty Leisner wrote:
> 
> I find it useful to  see the commands during failing builds
> (it started with samba, I also used this with proprietary products
> at work).
> 
> I added an -E flag which overrides .SILENT and @<command>
> to always echo the commands being done -- much better than running
> strace or hacking up the makefiles...
> 
> It was so easy, I should have done it much sooner!!
> (I've had this problem for more than a decade)!!
> 
> The patch is wrt 3.80, attached below:
> 
> Marty Leisner
> address@hidden
> 
>   ----------------------------------------------------------------------------
>                            Name: make.e-flag.diffs
>    make.e-flag.diffs       Type: Plain Text (text/plain)
>                     Description: make.e-flag.diffs
> 
>   ----------------------------------------------------------------------------
> _______________________________________________
> Bug-make mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-make