From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Cross compiling kernel module for the target
Date: Thu, 20 Dec 2018 10:20:59 +0100 [thread overview]
Message-ID: <20181220102059.1884d72d@windsurf> (raw)
In-Reply-To: <CA+OsCCRWydtsa1RVjGhc8ZdV-guMuA1ORauct4XH8ZYjgk6zvw@mail.gmail.com>
Hello,
On Thu, 20 Dec 2018 10:14:41 +0100, ?ukasz Przenios?o wrote:
> Thomas, sorry for the Cc, its there now.
> No, my module is supposed to be a completely separate thing for now. I
> intend to build it using cross compilation tools provided by build root
> after the image is loaded to the target. I want to load the module using
> insmod. Then after the module is stable, I could add it to the buildroot
> config.
You cannot build a kernel module out of nowhere, it has to be compiled
against a kernel source tree with configuration, or a kernel headers
tree with configuration. In the context of Buildroot, only the former
exists, so if you don't build your Linux kernel with Buildroot, you
cannot build a kernel module with Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-20 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 7:39 [Buildroot] Cross compiling kernel module for the target Łukasz Przeniosło
2018-12-20 8:04 ` Thomas Petazzoni
[not found] ` <CA+OsCCQ2TWYiEv-a8uRaJVSd4YX9A4T_EV1ihC1Y2ZyrNPAkag@mail.gmail.com>
2018-12-20 9:07 ` Thomas Petazzoni
2018-12-20 9:14 ` Łukasz Przeniosło
2018-12-20 9:20 ` Thomas Petazzoni [this message]
2018-12-20 9:34 ` Łukasz Przeniosło
2018-12-20 13:04 ` Thomas Petazzoni
2018-12-20 20:49 ` Łukasz Przeniosło
2018-12-20 21:04 ` Łukasz Przeniosło
2018-12-21 7:14 ` Łukasz Przeniosło
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=20181220102059.1884d72d@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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.