| 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
| ||
|
Date: Sun, 15 Mar 2009 11:12:10 +0100 From: Sam Ravnborg <sam@...nborg.org> To: Boaz Harrosh <bharrosh@...asas.com> Cc: linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: 2.6.29-rcx triviality - How to have foo.ko module with same name as foo.c source file On Sun, Mar 15, 2009 at 12:05:42PM +0200, Boaz Harrosh wrote: > Since sometime in the 2.6.29-rc I'm no longer able to produce an > out-of-tree module that has the same base-name as a source file. > > This is what I had in 2.6.28: > <Kbuild> > obj-m += foo.o > </Kbuild> > Where foo.c is a source file in the same directory. > > But since 2.6.29-rcx it will no longer build my foo.ko module. I > had to change it to: > <Kbuild> > foo_mod-y = foo.o > obj-m += foo_mod.o > </Kbuild> > Which changed my module name in scripts and packages. We use the single .c file for a module with the same name as the module all over the kernel. What is more likely is that your module started to include an additional sourcefile (antoehr .o) in which case you no longer can have a source file sharing the name of the module. > P.S: > Just asking I realized that I can just add an "mv ..." command to my make file. Using mv is no-no.. Sam -- 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