From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: rebuild after reconfiguring kernel
Date: Wed, 7 Jul 2010 14:09:32 +0200 [thread overview]
Message-ID: <20100707140932.63e1eb19@surf> (raw)
In-Reply-To: <201007061130.52946.hartleys@visionengravers.com>
Hello!
On Tue, 6 Jul 2010 11:30:52 -0700
H Hartley Sweeten <hartleys@visionengravers.com> wrote:
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 593a1b4..a014f55 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -139,6 +139,7 @@ linux26: host-module-init-tools $(LINUX26_DEPENDENCIES) $(LINUX26_DIR)/.stamp_in
>
> linux26-menuconfig linux26-xconfig linux26-gconfig: $(LINUX26_DIR)/.stamp_configured
> $(MAKE) $(LINUX26_MAKE_FLAGS) -C $(LINUX26_DIR) $(subst linux26-,,$@)
> + $(Q)touch $@
Unless I'm missing something, this change is going to create a
linux26-menuconfig file or a linux26-xconfig file, which is not
correct, and is not going to retrigger the build step of the kernel.
We are already handling the fact that the kernel should be rebuilt when
its configuration is changed. This is done through the following
dependency :
$(LINUX26_DIR)/.stamp_compiled: $(LINUX26_DIR)/.stamp_configured $(LINUX26_DIR)/.config
So, when the kernel .config is changed, the build step is restarted.
Which exact issue are you facing ? Can you provide an example ?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-07-07 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 18:30 [Buildroot] [PATCH] linux: rebuild after reconfiguring kernel H Hartley Sweeten
2010-07-07 12:09 ` Thomas Petazzoni [this message]
2010-07-07 20:11 ` H Hartley Sweeten
2010-07-08 7:31 ` Thomas Petazzoni
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=20100707140932.63e1eb19@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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