| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAO3ZPq2RUjW7VQQSoN-S7QDuTYdCMuDfoykHSeXwr19MTnCb_A@mail.gmail.com>
Date: Fri, 7 Oct 2011 10:20:46 -0700
From: Stephen Williams <steveicarus@...il.com>
To: linux-kernel@...r.kernel.org
Subject: Re: MODULE_LICENSE("GPL") not working for me
On Thu, Oct 6, 2011 at 3:30 PM, Stephen Williams <steveicarus@...il.com> wrote:
> 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. (right?) I'm using the following script to
> actually build:
More information: I can see that the vidfor.o object file, indeed
none of my *.o files, have a .modinfo section. In other situations
where the licens stamp works, the .modinfo section is present.
I'm using the CodeSourcery build of the arm toolchain, and in
the simple cases (module that is a single source file) the
modinfo information works. Hmm...
--
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."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists