From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel module compiled but not found
Date: Sun, 13 Oct 2013 19:05:03 +0200 [thread overview]
Message-ID: <525AD2BF.3000906@gmail.com> (raw)
In-Reply-To: <36BC54E98DCB453CA22ADF10A4AF6F94@JohanW7>
Il 13/10/2013 18:53, Sagaert Johan ha scritto:
> Just a caution:
> It's best to do a clean in a MYKMOD_CONFIGURE_CMDS section.
> I stumbled into this: the install path was not correct if the module had been build before.
> (In my case it was already build from within eclipse while developing.)
Hi,
I added the following section:
define SENSORAY2253_CONFIGURE_CMDS
$(MAKE) $(LINUX_MAKE_FLAGS) -C $(LINUX_DIR) M=$(@D) clean
endef
with no chance.
I tried also to remove the build/sensoray2253 directory and call:
make sensoray2253-reconfigure
make sensoray2253-rebuild
I cannot fine the ko file even in the build directory (I assume it is
copied to the install dir rather than moved). Anyway I would expect a
compiler error if the binary file is not created.
Mark
next prev parent reply other threads:[~2013-10-13 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 14:29 [Buildroot] Kernel module compiled but not found Marco Trapanese
2013-10-13 14:51 ` Yann E. MORIN
2013-10-13 15:02 ` Marco Trapanese
2013-10-13 15:05 ` Thomas Petazzoni
2013-10-13 15:19 ` Marco Trapanese
2013-10-13 21:12 ` Arnout Vandecappelle
2013-10-14 7:58 ` Marco Trapanese
2013-10-13 15:57 ` Yann E. MORIN
2013-10-13 16:53 ` Sagaert Johan
2013-10-13 17:05 ` Marco Trapanese [this message]
2013-10-13 15:56 ` Yann E. MORIN
2013-10-13 16:02 ` Marco Trapanese
2013-10-13 20:11 ` Ciarán Rehill
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=525AD2BF.3000906@gmail.com \
--to=marcotrapanese@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox