From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759235AbZCOKQW (ORCPT ); Sun, 15 Mar 2009 06:16:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757925AbZCOKQN (ORCPT ); Sun, 15 Mar 2009 06:16:13 -0400 Received: from gw-ca.panasas.com ([209.116.51.66]:9402 "EHLO laguna.int.panasas.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1757872AbZCOKQM (ORCPT ); Sun, 15 Mar 2009 06:16:12 -0400 Message-ID: <49BCD50B.4020501@panasas.com> Date: Sun, 15 Mar 2009 12:14:35 +0200 From: Boaz Harrosh User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Sam Ravnborg CC: linux-kernel Subject: Re: 2.6.29-rcx triviality - How to have foo.ko module with same name as foo.c source file References: <49BCD2F6.6030903@panasas.com> <20090315101210.GA5669@uranus.ravnborg.org> In-Reply-To: <20090315101210.GA5669@uranus.ravnborg.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Mar 2009 10:15:30.0590 (UTC) FILETIME=[F827D3E0:01C9A556] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sam Ravnborg wrote: > 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: >> >> obj-m += foo.o >> >> 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: >> >> foo_mod-y = foo.o >> obj-m += foo_mod.o >> >> 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 Hey hi, that was really fast ;) Thanks I realize that in-tree it works for sure. It's when I use the "make -M ..." out-of-tree and... No, I changed nothing, I had this, one liner, one source, one module and all of a sudden it does not build. Let me check if it is a dependency problem (not rebuilding when things change) or does it not build at all. Checking ... Boaz