From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 5918] New: Linux Kernel Headers Wrong Version
Date: Tue, 12 Feb 2013 01:51:40 +0000 (UTC) [thread overview]
Message-ID: <bug-5918-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=5918
Summary: Linux Kernel Headers Wrong Version
Product: buildroot
Version: unspecified
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: mihnen at mecmidwest.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Building with a custom git kernel the kernel headers that end up in the staging
directory to compile packages against are not from the kernel that I have
selected to build for the system.
I am building with an older 2.6.35 kernel from our own git repo but the kernel
headers that packages are compiled against are from a newer version. The
problem showed up when tslib wouldn't load because the ev version differed and
when I check the staging directory sure enough the include/linux/input.h has a
different EV_VERSION than my 2.6 kernel.
I'm not sure where its pulling the headers from? I did a little digging but
couldn't figure out where it attempts to find them.
This is from the 2012.11.1 release, I downloaded the git version as well and
the same problem exists. I am cross compiling for armv5te on i.mx28 evk with
codesourcery toolchain downloaded by buildroot. I'd be happy to implement a
patch if someone could point in the right direction for where to look in the
build system to find where it pulls in the kernel headers.
--
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:[~2013-02-12 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 1:51 bugzilla at busybox.net [this message]
2013-02-12 1:52 ` [Buildroot] [Bug 5918] Linux Kernel Headers Wrong Version bugzilla at busybox.net
2013-02-12 22:56 ` bugzilla at busybox.net
2013-02-13 7:52 ` 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-5918-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.