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 10796] New: Cannot generate cpio image without selecting CONFIG_BLK_DEV_INITRD
Date: Wed, 21 Feb 2018 21:23:28 +0000	[thread overview]
Message-ID: <bug-10796-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 10796
           Summary: Cannot generate cpio image without selecting
                    CONFIG_BLK_DEV_INITRD
           Product: buildroot
           Version: 2017.08
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: adyke at harris.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

If BR2_TARGET_ROOTFS_CPIO is selected, the next time linux-menuconfig is run
CONFIG_BLK_DEV_INITRD becomes selected. If CONFIG_BLK_DEV_INITRD is unselected,
it is silently reselected when linux-menuconfig exits.

Therefore, it is not possible to generate rootfs.cpio without building it into
the kernel image.

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

             reply	other threads:[~2018-02-21 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 21:23 bugzilla at busybox.net [this message]
2018-02-21 22:35 ` [Buildroot] [Bug 10796] Cannot generate cpio image without selecting CONFIG_BLK_DEV_INITRD bugzilla at busybox.net
2018-02-22 13:30 ` bugzilla at busybox.net
2018-02-25 16:05 ` 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-10796-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.