Received: from spf5.us4.outblaze.com (spf5.us4.outblaze.com [205.158.62.27]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id j0SFCL03005297 for ; Fri, 28 Jan 2005 15:12:22 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf5.us4.outblaze.com (Postfix) with ESMTP id 539E676E8A for ; Fri, 28 Jan 2005 15:12:57 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CuY0J-0002su-Bg for migo@homemail.com; Fri, 28 Jan 2005 10:25:47 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CuXzT-0002o6-L6 for gnu-arch-users@gnu.org; Fri, 28 Jan 2005 10:24:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CuXzK-0002jX-Nm for gnu-arch-users@gnu.org; Fri, 28 Jan 2005 10:24:46 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CuXzK-0002jG-Es for gnu-arch-users@gnu.org; Fri, 28 Jan 2005 10:24:46 -0500 Received: from [66.93.216.237] (helo=defaultvalue.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CuXlt-00082Y-I3 for gnu-arch-users@gnu.org; Fri, 28 Jan 2005 10:10:53 -0500 Received: from trouble.defaultvalue.org (omen.defaultvalue.org [192.168.1.1]) by defaultvalue.org (Postfix) with ESMTP id AFE294131 for ; Fri, 28 Jan 2005 09:10:52 -0600 (CST) Received: by trouble.defaultvalue.org (Postfix, from userid 1000) id 2A2E73C101A; Fri, 28 Jan 2005 09:10:52 -0600 (CST) To: gnu-arch-users@gnu.org Subject: Re: [Gnu-arch-users] What's the rationale behind the cmd-build-config.c restrictions? References: <87zmyu50ym.fsf@trouble.defaultvalue.org> <20050128141124.GD6045@suffields.me.uk> From: Rob Browning Date: Fri, 28 Jan 2005 09:10:52 -0600 In-Reply-To: <20050128141124.GD6045@suffields.me.uk> (Andrew Suffield's message of "Fri, 28 Jan 2005 14:11:24 +0000") Message-ID: <87pszpvbb7.fsf@trouble.defaultvalue.org> User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 1490 Lines: 50 Andrew Suffield writes: > On Thu, Jan 27, 2005 at 09:46:41AM -0600, Rob Browning wrote: >> >> In cmd-build-config.c we have: >> >> if (!arch_valid_config_name (config)) >> { >> safe_printfmt (2, "%s: invalid config name (%s)\n", >> argv[0], config); >> exit (2); >> } >> >> tree_root = arch_tree_root (0, dir, 0); >> >> if (!tree_root) >> { >> safe_printfmt (2, "%s: not in project tree (%s)\n", >> argv[0], dir); >> exit (1); >> } >> >> What's the rationale behind these restrictions? > > Nothing relevant, it's a bug. It's a very old bug that should have > been fixed a long time ago. Do you have any idea if the fix is likely to be as simple as removing that bit, or are there probably other changes that would need to be made? Also, do you know of anything I could do to help get this fixed? I'd be happy to try to generate a patch, but if the fix is as simple as removing the above, then I would imagine that a patch isn't likely to help. Thanks for the reply. -- Rob Browning rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4 _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/