This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: introduce common.m4
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 24 Apr 2013 14:12:37 -0600
- Subject: Re: RFC: introduce common.m4
- References: <871u9zomzd dot fsf at fleche dot redhat dot com> <51782A71 dot 7030305 at redhat dot com> <87obd3n4c8 dot fsf at fleche dot redhat dot com> <51782CC6 dot 9040008 at redhat dot com>
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> I think you misunderstood the question.
Indeed. Sorry about that.
>> The rule I propose is that if something is needed or used by common,
>> it should be checked for by common.m4; but that code outside this
>> directory also be free to use these results. This means that removing
>> checks from common.m4 must first be preceded by looking at uses in gdb
>> and gdbserver. I think this is pretty easy to do -- easier than what
>> we are doing now -- and I have documented the requirement.
Pedro> over keeping common aware of the checks it needs to do (in common.m4),
Pedro> and gdb/ and gdbserver/ also doing the checks they need for code under
Pedro> gdb/ and gdbserver/ respectively.
Pedro> Of course the current status of needing to update gdb and gdbserver in
Pedro> parallel for common/ things is no good.
Yeah, there is no deep reason for it other than wanting to avoid
duplicate checks. The cache would work fine for the performance aspect.
I can certainly just drop the configure.ac changes if you think that
yields a better result.
Tom