Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 22 Jun 2002 16:50:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 22 Jun 2002 16:50:43 -0400 Received: from [213.4.129.129] ([213.4.129.129]:63663 "EHLO tsmtp3.ldap.isp") by vger.kernel.org with ESMTP id ; Sat, 22 Jun 2002 16:50:42 -0400 Date: Sat, 22 Jun 2002 22:52:29 +0200 From: Diego Calleja To: Kai Germaschewski Cc: linux-kernel@vger.kernel.org Subject: Re: piggy broken in 2.5.24 build Message-Id: <20020622225229.46805a91.diegocg@teleline.es> In-Reply-To: References: <3D14B6DA.7090609@hotmail.com> X-Mailer: Sylpheed version 0.7.4 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1194 Lines: 29 Just a question about kbuild behaviour: I compiled 2.5.24, with make dep, make bzImage, make modules.... After that, as usually, make dep; make bzImage ...doesn't change nor recompile anything After that, I changed an option with menuconfig, "VGA 16-color graphics console support",and "3DFX Banshee/Voodoo 3 display support" (because i can't see somethnig when i boot with it) from built-in to module. Then I run make dep; and it did make some small changes, as expected. Then make bzImage compiled the entier kernel again, or at less a big big part of it, not only the changes made in menuconfig. make modules recompiled things again, wich are not affected with the changes (ie: iptables modules). My questions is: It's not expected to do the same as 2.4 kernels, i mean, recompile only the changes made, not the entire thing? PD: What are you doing with kbuild 2.5? What parts are you integrating? Wich parts you aren't going to integrate? - 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/