From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: GDB 9.1 release -- 2020-01-02 update
Date: Wed, 08 Jan 2020 00:34:00 -0000 [thread overview]
Message-ID: <CAPTJ0XEYuvYiMRouS9CXeT36XdU3EAWUJY5beA4dmVot6EMYDg@mail.gmail.com> (raw)
In-Reply-To: <20200102111623.GF5147@adacore.com>
On Thu, Jan 2, 2020 at 5:16 AM Joel Brobecker <brobecker@adacore.com> wrote:
> - [Christian] Unable to build GDB on recent MinGW due to _FORTIFY_SOURCE
> https://sourceware.org/ml/gdb-patches/2019-12/msg00787.html
>
> I hestitated a lot on the resolution of this issue, but
> in the end, I am OK with the proposed approach of not
> setting _FORTIFY_SOURCE on MinGW targets.
>
> I will send a comment on the thread in question.
I responded in that thread.
Unrelated: should we try to get a fix for
https://sourceware.org/bugzilla/show_bug.cgi?id=25190 in? The bug says
this is breaking cgdb. A patch was sent in
https://sourceware.org/ml/gdb-patches/2019-11/msg00859.html but it
seems like it needs work.
Christian
next prev parent reply other threads:[~2020-01-08 0:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 11:16 Joel Brobecker
2020-01-02 14:19 ` Joel Brobecker
2020-01-02 14:33 ` Eli Zaretskii
2020-01-08 0:34 ` Christian Biesinger via gdb-patches [this message]
2020-01-17 17:59 ` 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=CAPTJ0XEYuvYiMRouS9CXeT36XdU3EAWUJY5beA4dmVot6EMYDg@mail.gmail.com \
--to=gdb-patches@sourceware.org \
--cc=brobecker@adacore.com \
--cc=cbiesinger@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