All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <mulix@mulix.org>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>,
	Burton Windle <bwindle-kbt@fint.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix bug 376 - tiny extra echo in Makefile
Date: Thu, 20 Feb 2003 17:49:52 +0200	[thread overview]
Message-ID: <20030220154952.GB1202@actcom.co.il> (raw)
In-Reply-To: <Pine.LNX.4.44.0302200935590.19487-100000@chaos.physics.uiowa.edu>

On Thu, Feb 20, 2003 at 09:38:58AM -0600, Kai Germaschewski wrote:
> On Thu, 20 Feb 2003, Muli Ben-Yehuda wrote:
> 
> > --- a/Makefile	Thu Feb 20 13:40:59 2003
> > +++ b/Makefile	Thu Feb 20 13:40:59 2003
> > @@ -325,7 +325,7 @@
> >  define rule_vmlinux__
> >  	set -e
> >  	$(if $(filter .tmp_kallsyms%,$^),,
> > -	  echo '  Generating build number'
> > +	  @echo '  Generating build number'
> >  	  . $(src)/scripts/mkversion > .tmp_version
> >  	  mv -f .tmp_version .version
> >  	  $(Q)$(MAKE) $(build)=init
> 
> The thing is, I cannot reproduce it here.
> 
> Also, the entire rule_vmlinux__ is invoked with a '@' in front, so nothing
> there should be echoed. However, for the original submitter that obviously
> doesn't work, the ". $(src)..." line is echoed to. What version of "make"
> is used?

Burton, which make version are you using? on which distro? 

FWIW, I can't reproduce it here on RH 7.3 with make 3.79.1. Trying on
debian unstable now.
-- 
Muli Ben-Yehuda
http://www.mulix.org


  reply	other threads:[~2003-02-20 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 12:49 [PATCH] fix bug 376 - tiny extra echo in Makefile Muli Ben-Yehuda
2003-02-20 15:38 ` Kai Germaschewski
2003-02-20 15:49   ` Muli Ben-Yehuda [this message]
2003-02-20 17:25   ` Sam Ravnborg

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=20030220154952.GB1202@actcom.co.il \
    --to=mulix@mulix.org \
    --cc=bwindle-kbt@fint.org \
    --cc=kai@tp1.ruhr-uni-bochum.de \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.