public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Williams <steve@icarus.com>
To: linux-kernel@vger.kernel.org
Subject: MODULE_LICENSE("GPL") not working for me
Date: Thu, 06 Oct 2011 15:02:17 -0700	[thread overview]
Message-ID: <4E8E2569.8030301@icarus.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1911 bytes --]

I have some large drivers for use in embedded arm systems, and
I want them to be GPL, because I want to use some symbols exported
as GPL, and also because I just wanna. But it is not working for
me. I've attached my Makefile. I'm building from outside the kernel
tree, but that should be OK. I'm using the following script to
actually build:

  SE0=/home/u/wing/steve/picturel/SE0

CROSS_COMPILE=/opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-

  export CROSS_COMPILE
  make KERNELDIR=$SE0/linux-2.6.33-quatro ARCH=arm modules

But no matter what I do, when I try to load my module, I get
errors line this:

  # insmod ./vidfor2.ko
  vidfor: module license 'unspecified' taints kernel.
  Disabling lock debugging due to kernel taint
  vidfor: Unknown symbol driver_remove_file
  vidfor: Unknown symbol driver_create_file
  insmod: can't insert './vidfor2.ko': unknown symbol in module or
invalid parameter

I have a MODULE_LICENSE("GPL"); line in the "linux.c" source file,
and the pertinent parts of the makefile are here:

  OBJ := linux.o ops.o console.o sysfs.o ident_tables.o
  LIBOBJ := vidforio.o init.o format.o video.o isr.o version.o

  ifneq ($(KERNELRELEASE),)

  EXTRA_CFLAGS += -I$(M)/../libvidforio
  obj-m += vidfor.o
  vidfor-objs := $(OBJ) $(patsubst %,../libvidforio/%,$(LIBOBJ))

  else
  [...]

What's the trick for getting the MODULE_LICENSE successfully stamped
into my generated .ko file?

I've googled the list and the internet in general, and found
as many relevant examples as I could in the kernel source, but
I'm at wit's end. I'm not subscribed, so please CC responses,
although I will check back often.

-- 
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."

[-- Attachment #2: Makefile --]
[-- Type: text/plain, Size: 898 bytes --]



OBJ := linux.o ops.o console.o sysfs.o ident_tables.o
LIBOBJ := vidforio.o init.o format.o video.o isr.o version.o

ifneq ($(KERNELRELEASE),)

EXTRA_CFLAGS += -I$(M)/../libvidforio
obj-m += vidfor.o
vidfor-objs := $(OBJ) $(patsubst %,../libvidforio/%,$(LIBOBJ))

else

KERNELDIR ?= /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)

version ident_tables.c:
	@echo ' /* MACHINE GENERATED -- DO NOT EDIT */' > tmp.c
	@echo 'const char vidfor_build_stamp[] =' >> tmp.c
	@echo '"'`git describe --tags --long --always --match sys-\*`'";' >> tmp.c
	@diff tmp.c ident_tables.c > /dev/null 2>&1 || (echo "updating ident_tables.c"; cp tmp.c ident_tables.c)
	@rm -f tmp.c

modules:
	$(MAKE) -C ../libvidforio version
	$(MAKE) version
	$(MAKE) -C $(KERNELDIR) M=$(PWD) modules

modules_install:
	$(MAKE) -C $(KERNELDIR) M=$(PWD) modules_install

clean:
	$(MAKE) -C $(KERNELDIR) M=$(PWD) clean

endif

             reply	other threads:[~2011-10-06 22:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 22:02 Stephen Williams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-06 22:30 MODULE_LICENSE("GPL") not working for me Stephen Williams
2011-10-07  9:52 ` Arnd Bergmann
2011-10-07 17:20 ` Stephen Williams
2011-10-07 18:18   ` Sam Ravnborg
2011-10-08  0:36     ` Stephen Williams
2011-10-09  8:17       ` Sam Ravnborg

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=4E8E2569.8030301@icarus.com \
    --to=steve@icarus.com \
    --cc=linux-kernel@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