All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10506] New: Changing the kernel image type (e.g. zImage to uImage) does not take effect immediately
Date: Sun, 19 Nov 2017 07:38:08 +0000	[thread overview]
Message-ID: <bug-10506-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=10506

            Bug ID: 10506
           Summary: Changing the kernel image type (e.g. zImage to uImage)
                    does not take effect immediately
           Product: buildroot
           Version: 2017.02.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: gmichael225 at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

I may be missing something, but when I:

 - complete a build by running "make", then
 - change the kernel image type from zImage from uImage, or from uImage to
zImage, then
 - run "make" again

the newly requested image type is not created.

Running "make clean", before "make" does cause the image to be created (but
obviously that's a lot of recompiling!)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2017-11-19  7:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-19  7:38 bugzilla at busybox.net [this message]
2017-11-19  7:38 ` [Buildroot] [Bug 10506] Changed kernel image type (e.g. zImage to uImage) does not build on next "make" bugzilla at busybox.net
2017-11-19 15:01 ` bugzilla at busybox.net

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=bug-10506-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.