From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2725] New: Buildroot overrides kernel config
Date: Mon, 25 Oct 2010 12:57:26 +0000 (UTC) [thread overview]
Message-ID: <bug-2725-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2725
Summary: Buildroot overrides kernel config
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: chromy at asix.cz
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Buildroot overrides certain directives in kernel configuration.
Example: when doing a clean build, unless BR2_TARGET_ROOTFS_INITRAMFS in
Buildroot's config file is set, kernel is built without initramfs support
despite it was enabled in file referenced by
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE.
On the other hand if BR2_TARGET_ROOTFS_INITRAMFS is set, kernel image contains
complete root filesytem.
This is unacceptable - this way it is a problem to build kernel with initramfs
support but without actual filesystem embedded in the kernel, Buildroot shall
not be such invasive when custom configuration file is provided.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-10-25 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 12:57 bugzilla at busybox.net [this message]
2010-11-07 18:59 ` [Buildroot] [Bug 2725] Buildroot overrides kernel config 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-2725-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox