From: "Ciarán Rehill" <cir.vfi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel module compiled but not found
Date: Sun, 13 Oct 2013 21:11:34 +0100 [thread overview]
Message-ID: <1381695094.2543.10.camel@cabbage> (raw)
In-Reply-To: <525AAE63.3060601@gmail.com>
Marco Trapanese wrote:
...
> >>> sensoray2253 1.2.6 Building
> /usr/bin/make -j5
> HOSTCC="/home/mark/dev/rpiqt5/buildroot-rpi/output/host/usr/bin/ccache
> /usr/bin/gcc" HOSTCFLAGS="" ARCH=arm
> INSTALL_MOD_PATH=/home/mark/dev/rpiqt5/buildroot-rpi/output/target
> CROSS_COMPILE="/home/mark/dev/rpiqt5/buildroot-rpi/output/host/usr/bin/ccache
> /home/mark/dev/rpiqt5/buildroot-rpi/output/host/usr/bin/arm-buildroot-linux-gnueabi-"
> DEPMOD=/home/mark/dev/rpiqt5/buildroot-rpi/output/host/usr/sbin/depmod
> -C /home/mark/dev/rpiqt5/buildroot-rpi/output/build/linux-custom
> M=/home/mark/dev/rpiqt5/buildroot-rpi/output/build/sensoray2253-1.2.6
> modules
> make[1]: Entering directory
> `/home/mark/dev/rpiqt5/buildroot-rpi/output/build/linux-custom'
> Building modules, stage 2.
> MODPOST 0 modules
Zero modules makes me think that there's something up with your source
makefile (the one in output/build/sensoray...) You should probably post
it.
As you say, no errors - but nothing done either.
prev parent reply other threads:[~2013-10-13 20:11 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
2013-10-13 15:56 ` Yann E. MORIN
2013-10-13 16:02 ` Marco Trapanese
2013-10-13 20:11 ` Ciarán Rehill [this message]
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=1381695094.2543.10.camel@cabbage \
--to=cir.vfi@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 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.