From: Sam Ravnborg <sam@ravnborg.org>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: kbuild: Build minimum in scripts/ when changing configuration
Date: Wed, 10 Sep 2003 22:13:20 +0200 [thread overview]
Message-ID: <20030910201320.GA5852@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0309101555590.13584-100000@sweetums.bluetronic.net>
On Wed, Sep 10, 2003 at 03:58:02PM -0400, Ricky Beam wrote:
> On Wed, 10 Sep 2003, Sam Ravnborg wrote:
> >+scripts/fixdep:
> >+ $(Q)$(MAKE) $(build)=scripts $@
> >+
>
> Umm, that still doesn't address the "already up to date" make will generate
> when fixdep doesn't need to be rebuilt. (which is why I changed things the
> way I did.)
I am aware of that.
It does not happen in the usual situations where it would have become
visible.
One example is "make oldconfig" where it appears, but there is so much
other output that I avoided to introduce special support to avoid it.
You see the same with asm-offset.h. We could avoid that with a hack
in Makefile.build, but I have resisted to do it, again to avoid special cases.
Sam
next prev parent reply other threads:[~2003-09-10 20:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 19:14 [BK PATCHES] kbuild/kconfig Sam Ravnborg
2003-09-10 19:16 ` kbuild: Save relevant parts of modules.txt Sam Ravnborg
2003-09-10 19:17 ` kconfig: Allow architectures to select board specific configs Sam Ravnborg
2003-09-10 19:17 ` kbuild: Build minimum in scripts/ when changing configuration Sam Ravnborg
2003-09-10 19:58 ` Ricky Beam
2003-09-10 20:13 ` Sam Ravnborg [this message]
2003-09-10 21:00 ` Ricky Beam
2003-09-10 19:18 ` kbuild: Remove cscope.out during make mrproper Sam Ravnborg
2003-09-22 17:24 ` GOTO Masanori
2003-09-22 20:55 ` Sam Ravnborg
2003-09-10 19:18 ` kbuild/ppc*: Remove obsolete _config support Sam Ravnborg
2003-09-10 19:34 ` [BK PATCHES] kbuild/kconfig Russell King
2003-09-10 19:48 ` Sam Ravnborg
2003-09-10 22:13 ` Russell King
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=20030910201320.GA5852@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jfbeam@bluetronic.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox