Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 15 Mar 2003 23:58:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 15 Mar 2003 23:58:26 -0500 Received: from nat9.steeleye.com ([65.114.3.137]:37893 "EHLO hancock.sc.steeleye.com") by vger.kernel.org with ESMTP id ; Sat, 15 Mar 2003 23:58:25 -0500 Subject: Re: [patch] NUMAQ subarchification From: James Bottomley To: Kai Germaschewski Cc: "Martin J. Bligh" , colpatch@us.ibm.com, linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-9) Date: 15 Mar 2003 23:05:55 -0600 Message-Id: <1047791157.1963.212.camel@mulgrave> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 911 Lines: 26 On Sat, 2003-03-15 at 20:53, Kai Germaschewski wrote: > I think VPATH has never been meant to be used for anything like this, it > could be make to work, though it would interfere with the separate src/obj > thing. But I don't think it's a good idea, we'll have object files > magically appear without any visible source file, that's just too obscure. Well...There is a slightly different solution. What if the summit/numaq setup.c simply contained #include "../mach-default/setup.c" ? Not that I like doing this, but it solves the "magic" appearace of the object file and it's perfectly clear to anyone editing the file where it really comes from. James - 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/