From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Tom Tromey <tom@tromey.com>,
gdb-patches@sourceware.org
Subject: Re: [RFA] Add --enable-codesign to gdb's configure
Date: Thu, 28 Jun 2018 21:12:00 -0000 [thread overview]
Message-ID: <87bmbupqd4.fsf@tromey.com> (raw)
In-Reply-To: <20180628192051.GD2511@adacore.com> (Joel Brobecker's message of "Thu, 28 Jun 2018 12:20:51 -0700")
>> OK for the NEWS part, but I think we should reflect this option in the
>> output of "gdb --configure", because users will want to know whether
>> their GDB was configured that way.
Joel> The new option actually influences the build, not whether GDB provides
Joel> a given feature or not.
I'm not sure there's a way for gdb to know whether it's been signed, I
guess other than invoking codesign itself. I'm going to check this in,
but if it still needs the change, let me know and I will see if I can
implement it.
Tom
next prev parent reply other threads:[~2018-06-28 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 16:37 Tom Tromey
2018-06-28 17:31 ` Joel Brobecker
2018-06-28 18:31 ` Eli Zaretskii
2018-06-28 19:20 ` Joel Brobecker
2018-06-28 21:12 ` Tom Tromey [this message]
2018-06-29 22:19 ` Joel Brobecker
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=87bmbupqd4.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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