Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1945938AbWBDJNy (ORCPT ); Sat, 4 Feb 2006 04:13:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1945939AbWBDJNy (ORCPT ); Sat, 4 Feb 2006 04:13:54 -0500 Received: from einhorn.in-berlin.de ([192.109.42.8]:18318 "EHLO einhorn.in-berlin.de") by vger.kernel.org with ESMTP id S1945938AbWBDJNx (ORCPT ); Sat, 4 Feb 2006 04:13:53 -0500 X-Envelope-From: stefanr@s5r6.in-berlin.de Message-ID: <43E46F1F.9070503@s5r6.in-berlin.de> Date: Sat, 04 Feb 2006 10:08:47 +0100 From: Stefan Richter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040914 X-Accept-Language: de, en MIME-Version: 1.0 To: Adrian Bunk CC: Andrew Morton , bcollins@debian.org, scjody@modernduck.com, linux-kernel@vger.kernel.org, linux1394-devel@lists.sourceforge.ne, sam@ravnborg.org, Johannes Berg Subject: Re: 2.6.16-rc1-mm5: drivers/ieee1394/oui O=... builds broken References: <20060203000704.3964a39f.akpm@osdl.org> <20060203212507.GR4408@stusta.de> In-Reply-To: <20060203212507.GR4408@stusta.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: (-0.449) AWL,BAYES_40 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 793 Lines: 26 Adrian Bunk wrote: > ... > OUI2C drivers/ieee1394/oui.c > /bin/sh: drivers/ieee1394/oui2c.sh: No such file or directory > make[3]: *** [drivers/ieee1394/oui.c] Error 127 > > <-- snip --> > > > The change that broke it is: > > > quiet_cmd_oui2c = OUI2C $@ > - cmd_oui2c = $(CONFIG_SHELL) $(srctree)/$(src)/oui2c.sh < $< > $@ > + cmd_oui2c = $(CONFIG_SHELL) $(src)/oui2c.sh < $< > $@ How can this be reproduced? IOW which way of building the kernel is broken? -- Stefan Richter -=====-=-==- --=- --=-- http://arcgraph.de/sr/ - 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/