From: Mark Hounschell <dmarkh@cfl.rr.com>
To: frank.rowand@am.sony.com
Cc: markh@compro.net, linux-rt-users@vger.kernel.org
Subject: Re: external gpl kernel module build problem on 2.6.26.8-rt16
Date: Thu, 23 Apr 2009 06:49:03 -0400 [thread overview]
Message-ID: <49F0479F.70908@cfl.rr.com> (raw)
In-Reply-To: <49EF984C.50403@am.sony.com>
Frank Rowand wrote:
> Mark Hounschell wrote:
>> 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
>
> #define PICK_FUNCTION(type1, type2, func1, func2, arg0, ...) \
> do { \
> if (PICK_TYPE_EQUAL((arg0), type1)) \
> func1((type1)(arg0), ##__VA_ARGS__); \
> else if (PICK_TYPE_EQUAL((arg0), type2)) \
> func2((type2)(arg0), ##__VA_ARGS__); \
> else __bad_func_type(); \
> } while (0)
>
> And PICK_FUNCTION_RET() uses the same technique.
>
> Something that invokes PICK_FUNCTION() or PICK_FUNCTION_RET() is passing
> in an arg0 that is not type1 and is not type2.
>
> One easy way to figure out what is invoking PICK_FUNCTION()/PICK_FUNCTION_RET()
> is to look at the output from the cpp of your driver. The method I usually
> use is to add the flags "-C -E" to my compile command (and remove "-c").
> Then search the cpp output for __bad_func_type.
>
Thanks for the pointer. How might one do this using the kernel build system
though? Isn't the compile command used actually the kernels compile command?
Can I assume this would entail modifying the kernels top Makefile in some way?
Thanks again
Mark
next prev parent reply other threads:[~2009-04-23 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 20:55 external gpl kernel module build problem on 2.6.26.8-rt16 Mark Hounschell
2009-04-22 22:21 ` Frank Rowand
2009-04-23 10:49 ` Mark Hounschell [this message]
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=49F0479F.70908@cfl.rr.com \
--to=dmarkh@cfl.rr.com \
--cc=frank.rowand@am.sony.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=markh@compro.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;
as well as URLs for NNTP newsgroup(s).