From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/6] introduce common.m4
Date: Tue, 05 Nov 2013 18:23:00 -0000 [thread overview]
Message-ID: <1383675811-3274-1-git-send-email-tromey@redhat.com> (raw)
This series is an updated version of my earlier patch to add a
"common.m4":
https://sourceware.org/ml/gdb-patches/2013-04/msg00739.html
The idea behind common.m4 is to have all configury needed by common in
a single place. This avoids having to add parallel checks by hand to
both gdb and gdbserver's configure scripts.
I believe this version addresses Pedro's comments. Now the
"redundant" checks are not removed; instead, each configure script
checks for what it needs.
Eventually I think it makes sense to move gnulib, the common bits, and
gdbserver to be top-level subdirectories in src. This was difficult
before, due to CVS modules; but now it is much simpler to do, and I
think has benefits in terms of clarity and modularity. When this is
done, common.m4 will continue to exist, at least in the short term, so
that macros used by its headers are still properly defined by its
users.
Tom
next reply other threads:[~2013-11-05 18:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 18:23 Tom Tromey [this message]
2013-11-05 18:23 ` [PATCH v2 2/6] remove link.h checks Tom Tromey
2013-11-05 19:10 ` Pedro Alves
2013-11-05 18:24 ` [PATCH v2 1/6] introduce common.m4 Tom Tromey
2013-11-05 19:09 ` Pedro Alves
2013-11-05 20:03 ` Tom Tromey
2013-11-08 12:46 ` Pedro Alves
2013-11-08 19:32 ` Tom Tromey
2013-11-08 20:10 ` Tom Tromey
2013-11-05 18:25 ` [PATCH v2 4/6] gdb configure updates Tom Tromey
2013-11-05 19:10 ` Pedro Alves
2013-11-05 19:09 ` [PATCH v2 3/6] use gdb_string.h in m32c-tdep.c Tom Tromey
2013-11-05 19:49 ` Pedro Alves
2013-11-05 19:10 ` [PATCH v2 0/6] introduce common.m4 Pedro Alves
2013-11-05 20:04 ` [PATCH v2 5/6] fix a comment in configure.ac Tom Tromey
2013-11-05 21:10 ` [PATCH v2 6/6] remove unused gdbserver configury Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1383675811-3274-1-git-send-email-tromey@redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox