From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2137] New: Support rc versions of kernel headers
Date: Mon, 28 Jun 2010 16:44:16 +0000 (UTC) [thread overview]
Message-ID: <bug-2137-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2137
Summary: Support rc versions of kernel headers
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: will.newton at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
buildroot does not currently support building against rc versions of kernel
headers. The download step fails because the download directory differs between
rc and final kernel releases. This patch tries to detect when an rc kernel is
being used and download from the correct location.
--
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-06-28 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 16:44 bugzilla at busybox.net [this message]
2013-05-26 9:12 ` [Buildroot] [Bug 2137] Support rc versions of kernel headers 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-2137-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