From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10786] Linux fails to build unless make linux-menuconfig is run first
Date: Sun, 25 Feb 2018 21:38:06 +0000 [thread overview]
Message-ID: <bug-10786-163-gFp6rNHVTE@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10786-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10786
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
You have CONFIG_INITRAMFS_SOURCE defined in your linux_defconfig, but you have
not enabled initramfs support in Buildroot. So obviously this cannot work.
If you enable initramfs support in Buildroot, then Buildroot will make sure to
have a dummy rootfs.cpio when the kernel is first built, will make sure to set
CONFIG_INITRAMFS_SOURCE to the correct value, and will rebuild the kernel image
at the end of the build with the final rootfs.cpio.
Therefore, there is no bug per se: there is just a mis-use of the initramfs
support.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2018-02-25 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 20:01 [Buildroot] [Bug 10786] New: Linux fails to build unless make linux-menuconfig is run first bugzilla at busybox.net
2018-02-20 20:13 ` [Buildroot] [Bug 10786] " bugzilla at busybox.net
2018-02-21 22:56 ` bugzilla at busybox.net
2018-02-25 21:38 ` bugzilla at busybox.net [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=bug-10786-163-gFp6rNHVTE@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.