From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 129411 invoked by alias); 8 Jan 2020 00:34:38 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 129401 invoked by uid 89); 8 Jan 2020 00:34:38 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-17.0 required=5.0 tests=AWL,BAYES_00,ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_PASS,USER_IN_DEF_SPF_WL autolearn=ham version=3.3.1 spammy= X-HELO: mail-oi1-f180.google.com Received: from mail-oi1-f180.google.com (HELO mail-oi1-f180.google.com) (209.85.167.180) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 08 Jan 2020 00:34:36 +0000 Received: by mail-oi1-f180.google.com with SMTP id i1so1170765oie.8 for ; Tue, 07 Jan 2020 16:34:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=k/wa7dlYKswINoDtwBygMnl0C2ToPKED/3GWpNIhfZU=; b=LmYAk+HUtpYZtz24v1EnFuwO7WbVaH6nMpnsWRNuOaW24vMQZxSoKKD4hb+XStFqFU Q63cBcIrDusYhF2Y7NS2IHzyDFj9zL3C1R+Ywp5sGMbv+taPooDDbnHMEZf89pkc58Xs ILZSvQc5W3TQeua9Jt3AjrjXXIfS/A3BxkVv9jwVBy9UFxHayvJrdgmvvr+dhRJwZcXC yLEkkmQZIC+kxUYomV4VVjP0bKvrs/+gjC1rNFDdOvtXSbwbeOo/cAbLkYjlDvTDgT3U YbgBKCfrnMpTmaX+fWB+27+PH4beY+yGaIeJvXMcb1nPP9aGr8Eccuor4XlVet+KnDCV ounA== MIME-Version: 1.0 References: <20200102111623.GF5147@adacore.com> In-Reply-To: <20200102111623.GF5147@adacore.com> From: "Christian Biesinger via gdb-patches" Reply-To: Christian Biesinger Date: Wed, 08 Jan 2020 00:34:00 -0000 Message-ID: Subject: Re: GDB 9.1 release -- 2020-01-02 update To: Joel Brobecker Cc: gdb-patches Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2020-01/txt/msg00167.txt.bz2 On Thu, Jan 2, 2020 at 5:16 AM Joel Brobecker 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