From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: rebuild after reconfiguring kernel
Date: Thu, 8 Jul 2010 09:31:45 +0200 [thread overview]
Message-ID: <20100708093145.4bc1d0b9@surf> (raw)
In-Reply-To: <0D753D10438DA54287A00B02708426976373A92CA9@AUSP01VMBX24.collaborationhost.net>
On Wed, 7 Jul 2010 15:11:50 -0500
H Hartley Sweeten <hartleys@visionengravers.com> wrote:
> > 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.
>
> Argh... Your correct. The .stamp_configured file is the one that needs touched.
Right.
> > Which exact issue are you facing ? Can you provide an example ?
>
> Your correct, when the .config file is changed the kernel does rebuild.
>
> The strange thing is, yesterday it didn't work and I haven't changed anything.
> I would do:
>
> $ make linux26-menuconfig
>
> Change something in the config, then:
>
> $ make
>
> Or
>
> $ make linux26
>
> And the kernel would not rebuild. But if I did:
>
> $ touch output/build/linux-2.6.34/.stamp_configured
> $ make
>
> It would.
>
> Oh well, it's working now...
Strange. If you manage to reproduce something like this, don't hesitate
to tell us.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-07-08 7:31 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
2010-07-07 20:11 ` H Hartley Sweeten
2010-07-08 7:31 ` Thomas Petazzoni [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=20100708093145.4bc1d0b9@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 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.