From: Tristan Gingold <gingold@adacore.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA-Darwin]: Add an info key in darwin executable
Date: Tue, 06 Oct 2009 08:27:00 -0000 [thread overview]
Message-ID: <CE2BB5EF-595F-4A64-B6B1-C553E437B9A4@adacore.com> (raw)
In-Reply-To: <8ac60eac0910052118j7f3894fek22b6fa3b891118b1@mail.gmail.com>
On Oct 6, 2009, at 6:18 AM, Paul Pluzhnikov wrote:
> On Mon, Oct 5, 2009 at 5:22 AM, Tristan Gingold
> <gingold@adacore.com> wrote:
>
>> I think we should let the user or the system administrator signing
>> the
>> executable by itself as we can't create and publish a certificate.
>
> I have tried and failed to find info on just how to do such
> signing :-(
>
> Would you mind writing instructions somewhere in GDB wiki,
> and reference that page here:
I added a wiki page:
http://sourceware.org/gdb/wiki/BuildingOnDarwin
Feel free to improve it!
prev parent reply other threads:[~2009-10-06 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 12:22 Tristan Gingold
2009-10-05 17:30 ` Joel Brobecker
2009-10-06 12:26 ` Tristan Gingold
2009-10-06 15:07 ` Joel Brobecker
2009-10-06 4:18 ` Paul Pluzhnikov
2009-10-06 8:27 ` Tristan Gingold [this message]
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=CE2BB5EF-595F-4A64-B6B1-C553E437B9A4@adacore.com \
--to=gingold@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.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