Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 22 Jun 2002 17:24:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 22 Jun 2002 17:24:20 -0400 Received: from chaos.physics.uiowa.edu ([128.255.34.189]:57067 "EHLO chaos.physics.uiowa.edu") by vger.kernel.org with ESMTP id ; Sat, 22 Jun 2002 17:24:19 -0400 Date: Sat, 22 Jun 2002 16:24:13 -0500 (CDT) From: Kai Germaschewski X-X-Sender: kai@chaos.physics.uiowa.edu To: Riley Williams cc: Henning Makholm , "Adam J. Richter" , , Linux Ham Radio , Linux Kernel , Subject: Re: make-3.79.1 bug breaks linux-2.5.24/drivers/net/hamradio/soundmodem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 22 Jun 2002, Riley Williams wrote: > >> $(obj)/sm_tbl_%: $(obj)/gentbl > >> PATH=$(obj):$$PATH $< > > > That looks like an excessively complicated workaround. Why not just > > > > $(obj)/sm_tbl_%: $(obj)/gentbl > > $(obj)/gentbl > > > > instead ? I think I like the latter better as well. Anyway, $(obj) is just "." currently, so it doesn't have a space in it. For $(src), I'll always use relative paths, so there won't be any spaces in them either. I think it's a sensible restriction for separate src/obj trees to disallow spaces in the obj tree path, I fear it'd cause problems at a huge number of places. At least it's certainly acceptable to do "no space" first and then see what needs to be done in order to remove that restriction. (I also think the two are functionally equivalent even if $(obj) contains a space, but I haven't tried at all) --Kai - 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/