Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265903AbUFOTrJ (ORCPT ); Tue, 15 Jun 2004 15:47:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265891AbUFOTrJ (ORCPT ); Tue, 15 Jun 2004 15:47:09 -0400 Received: from pfepc.post.tele.dk ([195.41.46.237]:27156 "EHLO pfepc.post.tele.dk") by vger.kernel.org with ESMTP id S265890AbUFOTq3 (ORCPT ); Tue, 15 Jun 2004 15:46:29 -0400 Date: Tue, 15 Jun 2004 21:55:42 +0200 From: Sam Ravnborg To: Jari Ruusu Cc: Sam Ravnborg , Andrew Morton , linux-kernel@vger.kernel.org, Linus Torvalds Subject: Re: [PATCH 5/5] kbuild: external module build doc Message-ID: <20040615195542.GE2310@mars.ravnborg.org> Mail-Followup-To: Jari Ruusu , Sam Ravnborg , Andrew Morton , linux-kernel@vger.kernel.org, Linus Torvalds References: <20040614204029.GA15243@mars.ravnborg.org> <20040614204809.GF15243@mars.ravnborg.org> <40CF4C48.5A317311@users.sourceforge.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40CF4C48.5A317311@users.sourceforge.net> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2296 Lines: 55 On Tue, Jun 15, 2004 at 10:21:44PM +0300, Jari Ruusu wrote: > Sam Ravnborg wrote: > > --- /dev/null Wed Dec 31 16:00:00 196900 > > +++ b/Documentation/kbuild/extmodules.txt 2004-06-14 22:25:21 +02:00 > [snip] > > +A more advanced example > > +- - - - - - - - - - - - > > +This example shows a setup where a distribution has wisely decided > > +to separate kernel source and output files: > > + > > +Kernel src: > > +/usr/src/linux-/ > > + > > +Output from a kernel compile, including .config: > > +/lib/modules/linux-/build/ > ^^^^^ > Wrong! The 'build' symlink has always pointed to kernel source dir in > separate source and object directory case. This document was written before Andreas posted his patch - I just never came around updating it. ^^^^^^ > Sam, You don't seem to have any idea how much breakage you introduce if you > insist on redirecting the 'build' symlink from source tree to object tree. No - and I still do not see it. Please explain how we can be backward compatible when vendors start utilising separate directories for src and output. Anyway, after I gave it some extra thoughs I concluded that /lib/modules/kernel-/ was the wrong place to keep info about where to src for a given build is located. This information has to stay in the output directory. So what I will implement is that during the kernel build process (not the install part) a symlink named 'source' is placed in the root of the output directory - and links to the root of the kernel src used for building the kernel. Then /lib/modules/kernel-/build/source will be where the source is located. And /lib/modules/kernel-/build will point to the output files. If the vendor does not utilise separate src and output directories they will point to the same directory. If the vendor utilises separate output and source directories then thay will point in two different places. Comments? Sam - 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/