From: Mark Hounschell <markh@compro.net>
To: linux-rt-users@vger.kernel.org
Subject: external gpl kernel module build problem on 2.6.26.8-rt16
Date: Wed, 22 Apr 2009 16:55:37 -0400 [thread overview]
Message-ID: <49EF8449.2030000@compro.net> (raw)
I get the following while trying to build this driver. What does it mean.
Building modules, stage 2.
MODPOST 1 modules
WARNING: "__bad_func_type" [/local/work/markh/pci5565-linux/driver/rfm2g.ko]
undefined!
Then obviously the module doesn't load for the same reason.
When I grep the kernel for bad_func_type all I see is
include/linux/rt_lock.h:192:extern int __bad_func_type(void);
include/linux/pickop.h:8:extern int __bad_func_type(void);
include/linux/pickop.h:16: else __bad_func_type();
\
include/linux/pickop.h:27: else __ret = __bad_func_type();
Any help or hints would be appreciated
Thanks in advance
Mark
next reply other threads:[~2009-04-22 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 20:55 Mark Hounschell [this message]
2009-04-22 22:21 ` external gpl kernel module build problem on 2.6.26.8-rt16 Frank Rowand
2009-04-23 10:49 ` Mark Hounschell
2009-04-23 11:56 ` Uwe Kleine-König
2009-04-23 15:14 ` Mark Hounschell
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=49EF8449.2030000@compro.net \
--to=markh@compro.net \
--cc=linux-rt-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).