Re: [Gnu-arch-users] What's the rationale behind the cmd-build-config.c restrictions?

[Rob Browning]

Andrew Suffield <address@hidden> 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