From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, pmuldoon@redhat.com
Subject: Re: [PATCH v4 2/2] compile: Add 'set compile-gcc'
Date: Sun, 24 May 2015 19:31:00 -0000 [thread overview]
Message-ID: <83vbfhzsax.fsf@gnu.org> (raw)
In-Reply-To: <20150524185800.31862.67584.stgit@host1.jankratochvil.net>
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Phil Muldoon <pmuldoon@redhat.com>
> Date: Sun, 24 May 2015 20:58:00 +0200
>
> gdb/doc/ChangeLog
> 2015-05-24 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * doc/gdb.texinfo (Compiling and Injecting Code): Add to subsection
> Compiler search for the compile command descriptions of set
> compile-gcc and show compile-gcc.
Please have the subsection name in quotes.
> +set|show compile-gcc
> + Set and show compilation command used for compiling and injecting code
> + with the compile commands.
^^^^^^^
'compile'
> + add_setshow_filename_cmd ("compile-gcc", class_support,
> + &compile_gcc,
> + _("Set compile command GCC driver filename"),
> + _("Show compile command GCC driver filename"),
> + _("\
> +It should be absolute pathname to the gcc executable.\n\
^^^^^^^^^^^
"filename of"
> +If set, it is the main command @code{gcc}, found usually for example
^^^^^
@command
> +under name @code{x86_64-linux-gnu-gcc}.
^^^^^
@file
OK with those fixed.
Thanks.
next prev parent reply other threads:[~2015-05-24 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 18:58 [PATCH v4 1/2] compile: set debug compile: Display GCC driver filename Jan Kratochvil
2015-05-24 18:58 ` [PATCH v4 2/2] compile: Add 'set compile-gcc' Jan Kratochvil
2015-05-24 19:31 ` Eli Zaretskii [this message]
2015-05-25 18:50 ` [PATCH v5 " Jan Kratochvil
2015-05-29 11:02 ` Pedro Alves
2015-05-29 11:02 ` [PATCH v4 1/2] compile: set debug compile: Display GCC driver filename 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=83vbfhzsax.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pmuldoon@redhat.com \
/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