Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 26 Jan 2003 18:11:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 26 Jan 2003 18:11:31 -0500 Received: from [213.86.99.237] ([213.86.99.237]:18142 "EHLO passion.cambridge.redhat.com") by vger.kernel.org with ESMTP id ; Sun, 26 Jan 2003 18:11:30 -0500 X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: David Woodhouse X-Accept-Language: en_GB In-Reply-To: <20030127000740.GJ394@kugai> References: <20030127000740.GJ394@kugai> <20030126231232.GE394@kugai> <20030126215714.GA394@kugai> <30633.1043621749@passion.cambridge.redhat.com> To: Christian Zander Cc: Kai Germaschewski , Mark Fasheh , Thomas Schlichter , "Randy.Dunlap" , Sam Ravnborg , LKML , Rusty Russell Subject: Re: no version magic, tainting kernel. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 Jan 2003 23:16:11 +0000 Message-ID: <31172.1043622971@passion.cambridge.redhat.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org zander@minion.de said: > I apologize if I have argued based on false assumptions; is it true > then that a Makefile written for use with Linux 2.5 kbuild will work > unchanged with any Linux 2.2/2.5 kernel (w/ custom CFLAGS, ...)? There are some differences, but nothing insurmountable. For <=2.4 you have to include Rules.make at the end of your own Makefile, and for 2.5 that file doesn't exist any more. For older kernels you must set O_TARGET, for 2.5 I think the mere act of setting it causes the build to break -- that one is gratuitously making it harder to make external modules which compile in both and I've complained about it before. Per-file CFLAGS must have a full path specified now in 2.5, whereas in 2.4 and earlier it was just 'CFLAGS_filename.o'. -- dwmw2 - 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/