public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: Sam Ravnborg <linux-kbuild@vger.kernel.org>
Subject: Re: shell command is empty, when "silent" (Re: make V=1 broken)
Date: Mon, 11 Feb 2008 15:32:47 +0100	[thread overview]
Message-ID: <20080211143247.GH24008@flower.upol.cz> (raw)
In-Reply-To: <20080211133453.GC20959@uranus.ravnborg.org>

On Mon, Feb 11, 2008 at 02:34:53PM +0100, Sam Ravnborg wrote:
> On Mon, Feb 11, 2008 at 03:46:40AM +0100, Oleg Verych wrote:
[]
> > ,--`make V=1`--
> > |  GEN     /dev/shm/blinux/Makefile
> > |set -e; ; mkdir -p include/linux/; 
> > []
> > |/bin/sh: Syntax error: ";" unexpected
> > `--
> > 
> > That "silent" juggling with `echo` is overhead, thus remove it.
> 
> Hi Oleg.
> People has requested to make the build even more silent with
> make -s. So when Mike provided a patch is was applied (but unfortunately faulty).
> 
> So I fixed it by appended patch.
> The right fix would have been to resue echo-cmd but that
> required a bit more rework.
[]

Memory is cheap, efficiency is uselsess.

Funny, that *debug* output didn't give a clue for quite some people.

Aah, why do i care?

>  #   to specify a valid file as first prerequisite (often the kbuild file)
> +       chk_filechk = :
>   quiet_chk_filechk = echo '  CHK     $@'
>  silent_chk_filechk = :
> +       upd_filechk = :
>   quiet_upd_filechk = echo '  UPD     $@'
>  silent_upd_filechk = :
> +
>  define filechk
>  	$(Q)set -e;				\
>  	$($(quiet)chk_filechk);			\
> -- 
> 1.5.4.rc3.14.g44397
> 

      reply	other threads:[~2008-02-11 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 22:59 make V=1 broken Sam Ravnborg
2008-02-11  2:46 ` shell command is empty, when "silent" (Re: make V=1 broken) Oleg Verych
2008-02-11 13:34   ` Sam Ravnborg
2008-02-11 14:32     ` Oleg Verych [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080211143247.GH24008@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --cc=linux-kbuild@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox