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 09:04:11 +0100 [thread overview]
Message-ID: <20181220090411.7ab00f70@windsurf> (raw)
In-Reply-To: <CA+OsCCTCqQ+Fne+=VtXKgi5E_ezkdTAva-zTk6KaWa9egem0Sg@mail.gmail.com>
Hello,
On Thu, 20 Dec 2018 08:39:26 +0100, ?ukasz Przenios?o wrote:
> obj-m := simp.o
> KERNELDIR ?= /home/lukasz/brl/Machine/beaglebone/build/linux-headers-a75d8e93056181d512f6c818e8627bd4554aaf92
This should point to output/build/linux-<version>/ and not
output/build/linux-headers-<version>/.
> CC [M] /tmp/test/simp.o
> In file included from <command-line>:0:0:
> ././include/linux/kconfig.h:4:32: fatal error: generated/autoconf.h:
> No such file or directory
> #include <generated/autoconf.h>
As explained above, this is because you're using the linux-headers
source, which is not "configured" (i.e no kernel configuration has been
applied to it), and building a kernel module requires a configured
source tree.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-20 8:04 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 [this message]
[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
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=20181220090411.7ab00f70@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.