From: Pedro Alves <alves.ped@gmail.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdbserver: install gdbreplay too
Date: Mon, 02 Jan 2012 12:47:00 -0000 [thread overview]
Message-ID: <4F01A735.8080503@gmail.com> (raw)
In-Reply-To: <1325321888-5293-1-git-send-email-vapier@gentoo.org>
On 12/31/2011 08:58 AM, Mike Frysinger wrote:
> The gdbreplay binary is pretty useful, so install it by default like we
> do with gdbserver already.
I'm ambivalent on this. This is a gdb developer tool, not something a
user would use.
>
> Signed-off-by: Mike Frysinger<vapier@gentoo.org>
>
> 2011-12-31 Mike Frysinger<vapier@gentoo.org>
>
> * Makefile.in (install): Install gdbreplay into $(bindir).
> ---
> gdb/gdbserver/Makefile.in | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/gdb/gdbserver/Makefile.in b/gdb/gdbserver/Makefile.in
> index 01729ce..1ce196a 100644
> --- a/gdb/gdbserver/Makefile.in
> +++ b/gdb/gdbserver/Makefile.in
> @@ -213,6 +213,8 @@ install-only:
> $(INSTALL_PROGRAM) gdbserver$(EXEEXT) $(DESTDIR)$(bindir)/$$n$(EXEEXT); \
> $(SHELL) $(srcdir)/../../mkinstalldirs $(DESTDIR)$(man1dir); \
> $(INSTALL_DATA) $(srcdir)/gdbserver.1 $(DESTDIR)$(man1dir)/$$n.1
> + n=`echo gdbreplay | sed '$(program_transform_name)'`; \
> + $(INSTALL_PROGRAM) gdbreplay$(EXEEXT) $(DESTDIR)$(bindir)/$$n$(EXEEXT); \
>
> uninstall: force
> n=`echo gdbserver | sed '$(program_transform_name)'`; \
next prev parent reply other threads:[~2012-01-02 12:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 9:13 Mike Frysinger
2011-12-31 14:25 ` Joel Brobecker
2012-01-01 20:36 ` Jan Kratochvil
2012-01-02 12:47 ` Pedro Alves [this message]
2012-01-03 2:30 ` Mike Frysinger
2012-01-03 2:58 ` Joel Brobecker
2012-01-03 7:46 ` Joel Brobecker
2012-01-04 12:48 ` Pedro Alves
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=4F01A735.8080503@gmail.com \
--to=alves.ped@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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