From: Javier Casas Marin <jcasas@wifense.com>
To: backports@vger.kernel.org
Subject: Error compiling backports-3.16-1 on a device with a 2.6.30 kernel
Date: Tue, 02 Sep 2014 18:48:49 +0200 [thread overview]
Message-ID: <5405F4F1.1050808@wifense.com> (raw)
I am trying to compile backports-3.16-1 on a device with a 2.6.30 linux
kernel and I get this error:
$ make
CC [M] /root/modules/backports-3.16-1/compat/main.o
In file included from
/root/modules/backports-3.16-1/backport-include/linux/kernel.h:9,
from
/mnt/cfdata/src/linux-2.6.30/arch/x86/include/asm/system.h:10,
from
/mnt/cfdata/src/linux-2.6.30/arch/x86/include/asm/processor.h:17,
from include/linux/prefetch.h:14,
from include/linux/list.h:6,
from
/root/modules/backports-3.16-1/backport-include/linux/list.h:3,
from include/linux/module.h:9,
from
/root/modules/backports-3.16-1/backport-include/linux/module.h:3,
from /root/modules/backports-3.16-1/compat/main.c:1:
/root/modules/backports-3.16-1/backport-include/linux/printk.h:5:31:
error: linux/printk.h: No such file or directory
make[6]: *** [/root/modules/backports-3.16-1/compat/main.o] Error 1
make[5]: *** [/root/modules/backports-3.16-1/compat] Error 2
make[4]: *** [_module_/root/modules/backports-3.16-1] Error 2
make[3]: *** [modules] Error 2
make[2]: *** [modules] Error 2
make[1]: *** [modules] Error 2
make: *** [default] Error 2
it looks like I can't compile it for kernel 2.6.30 because some headers
files are missing (printk.h was inside kernel.h in previous kernel
versions like in 2.6.30). But the documentation says that kernels 2.6.27
and older are supported, so what am I doing wrong?
please, I'm stuck, any hint or information will be very appreciated!
Thanks
next reply other threads:[~2014-09-02 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 16:48 Javier Casas Marin [this message]
2014-09-02 21:36 ` Error compiling backports-3.16-1 on a device with a 2.6.30 kernel Hauke Mehrtens
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=5405F4F1.1050808@wifense.com \
--to=jcasas@wifense.com \
--cc=backports@vger.kernel.org \
/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.