Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263585AbUFTVHv (ORCPT ); Sun, 20 Jun 2004 17:07:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265946AbUFTVHv (ORCPT ); Sun, 20 Jun 2004 17:07:51 -0400 Received: from pfepc.post.tele.dk ([195.41.46.237]:42540 "EHLO pfepc.post.tele.dk") by vger.kernel.org with ESMTP id S263585AbUFTVHt (ORCPT ); Sun, 20 Jun 2004 17:07:49 -0400 Date: Sun, 20 Jun 2004 23:19:06 +0200 From: Sam Ravnborg To: Andrew Morton , Linus Torvalds Cc: linux-kernel@vger.kernel.org, Andreas Gruenbacher , Geert Uytterhoeven , Kai Germaschewski , Sam Ravnborg Subject: [PATCH 0/2] kbuild updates Message-ID: <20040620211905.GA10189@mars.ravnborg.org> Mail-Followup-To: Andrew Morton , Linus Torvalds , linux-kernel@vger.kernel.org, Andreas Gruenbacher , Geert Uytterhoeven , Kai Germaschewski Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1823 Lines: 39 Hi Andrew, Linus. Here follows two kbuild patches. 1) Add generic infrastructure for creating kernel packages. This moves make rpm support to scripts/package and add the deb-pkg target. The infrastructure were added because there is requests to add .tar.gz, .tar.gz2 support as well, and the functionality really did not belong in the top-level makefile. The implementation is simplified based on feedback on first patch, so one just have to set KBUILD_IMAGE in arch Makefiel to say what kernel image to include in the package. 2) Improved support for external modules. It has been debated what to name the symlink in /lib/modules/`uname -r` and where it should point. Now that there is a possibility to build the kernel with a separate output directory, there is a need to utilise this in the install. From now on build will point to the output directory, and source will point to the kernel source. A small MAkefile is created in the output directory allowing external modules to continue to build independent of the kernel being built with separate output directory, or with ouput and source mixed. If the kernel is build with source and output mixed there is no change in behaviour. If the kernel is build with separate source and output directories, all external modules that has not yet picked up on using the kbuild infrastructure will fail... No effort whatsoever will be done to keep external modules working if they do not use the kbuild infrastructure. There is no reason not to do so. 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/