From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3391] New: Add support for specifying an external kernel tree
Date: Mon, 7 Mar 2011 16:04:53 +0000 (UTC) [thread overview]
Message-ID: <bug-3391-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=3391
Summary: Add support for specifying an external kernel tree
Product: buildroot
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: mort at bork.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 3079
--> https://bugs.busybox.net/attachment.cgi?id=3079
external kernel tree patch
I didn't get any comments from the list, so I'm posting this here so I doesn't
get lost. One thing that I changed from my original post is to conditionally
create
the .stamp_{downloaded,extracted,patched} files. Doing do unconditionally
causes unnecessary invocation of make in the kernel directory during each
rebuild.
From my RFC e-mail to the buildroot list:
I wanted to compile a kernel from an external git tree, so adding
support for using this tree as the kernel source for buildroot
seemed logical.
The thing I'm seeking comments on is my short-circuiting of
the .stamp_{downloaded,extraced,patched} bits. Can someone
suggest a more elegant way of doing this?
..I removed patching support, since you should probably be using
some other tool to manage patches in the external tree anyways.
Comments appreciated
--
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:[~2011-03-07 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 16:04 bugzilla at busybox.net [this message]
2011-03-07 18:55 ` [Buildroot] [Bug 3391] Add support for specifying an external kernel tree bugzilla at busybox.net
2011-03-07 19:18 ` bugzilla at busybox.net
2011-09-18 9:49 ` bugzilla at busybox.net
2011-10-09 20:45 ` 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-3391-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