Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756440AbXIEKDO (ORCPT ); Wed, 5 Sep 2007 06:03:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755640AbXIEKC7 (ORCPT ); Wed, 5 Sep 2007 06:02:59 -0400 Received: from sovereign.computergmbh.de ([85.214.69.204]:50376 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755454AbXIEKC6 (ORCPT ); Wed, 5 Sep 2007 06:02:58 -0400 Date: Wed, 5 Sep 2007 12:02:57 +0200 (CEST) From: Jan Engelhardt To: "Robert P. J. Day" cc: Michal Piotrowski , Linux Kernel Mailing List , Sam Ravnborg , Roman Zippel Subject: Re: building a specific in-tree module is currently a bit broken In-Reply-To: Message-ID: References: <6bffcb0e0709050237m7d948782iffec36253c6fccb2@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1116 Lines: 29 On Sep 5 2007 05:42, Robert P. J. Day wrote: >that doesn't solve the problem. i should have mentioned that i >already (unnecessarily, i suggest) ran "make modules_prepare", but the >problem persists. > >the issue seems to be that running that last make command to build the >module visor.ko doesn't somehow signal the Makefile that this is a >*module* build, and therefore no module-related initialization is >done, such as creating that directory or setting the Makefile variable >MODVERDIR, etc, etc. ah... make M=drivers/foo/bar/ it builds the whole directory, but at least it builds it. > >once you've build at least one module successfully, then the directory >.tmp_versions exists so future module builds will work fine. it's >only when you do a clean, *immediately* followed by trying to do an >in-tree module build, that this is going to bite you. Jan -- - 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/