Messages in this thread | | | From | Keith Owens <> | Subject | Re: GPLONLY kernel symbols??? | Date | Wed, 17 Oct 2001 12:17:39 +1000 |
| |
On Tue, 16 Oct 2001 09:27:55 -0700 (PDT), Christoph Lameter <christoph@lameter.com> wrote: >I just tried to load the loop driver in 2.4.11 > >devel:/home/christoph/devel/bf/boot-floppies# insmod loop >Using /lib/modules/2.4.11/kernel/drivers/block/loop.o >/lib/modules/2.4.11/kernel/drivers/block/loop.o: unresolved symbol >invalidate_bdev >/lib/modules/2.4.11/kernel/drivers/block/loop.o: Note: modules without a >GPL compatible license cannot use GPLONLY_ symbols > >What is THAT?
If a symbol has been exported with EXPORT_SYMBOL_GPL then it appears as unresolved for modules that do not have a GPL compatible MODULE_LICENCE string. So when a module without a GPL compatible MODULE_LICENCE gets an unresolved symbol, I print that message as a hint to the user. I thought the response was obvious, but looks like I need to expand the hint text even further.
Note: modules without a GPL compatible license cannot use GPLONLY_ symbols. This may or may not be your problem, there can be other reasons for unresolved symbols.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |