From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26029 invoked by alias); 2 Jan 2020 11:16:30 -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 26013 invoked by uid 89); 2 Jan 2020 11:16:30 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=Christian, official, year, revert X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 02 Jan 2020 11:16:29 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id BD6A9117127 for ; Thu, 2 Jan 2020 06:16:27 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id RYZBCkjFBKwN for ; Thu, 2 Jan 2020 06:16:27 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 589B81170DB for ; Thu, 2 Jan 2020 06:16:27 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 16816838B8; Thu, 2 Jan 2020 15:16:23 +0400 (+04) Date: Thu, 02 Jan 2020 11:16:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Subject: GDB 9.1 release -- 2020-01-02 update Message-ID: <20200102111623.GF5147@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.4 (2018-02-28) X-SW-Source: 2020-01/txt/msg00018.txt.bz2 Hi everyone, Happy New Year! Am I the only one wondering where the End of Year Holidays went?!? Quick status update, based on feedback for the branch, so far. Added since the last update: - [Joel/Tom/Simon] Report error if trying to build GDB in tree https://www.sourceware.org/ml/gdb/2019-12/msg00034.html I think this is an acceptable limitation, but we haven't really made the official decision that it is. If we do, then we can patch configure to just report a clear error. Tom suggested an alternative, which is to revert the gnulib move on the branch. From my perspective, this is less desirable, because it is a riskier move. - [Andrew] unexpected disassembly output in backtrace https://sourceware.org/ml/gdb-patches/2019-12/msg01007.html - [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. Still Open: - [Eliz] libtcf fails to build on MinGW https://sourceware.org/bugzilla/show_bug.cgi?id=25155 Problem reported to binutils on Dec 17th, but so far no answer as far as I can tell. https://sourceware.org/ml/binutils/2019-12/msg00277.html Joel to send a copy of the patch to binutils, which should make it easier for people to review, compared to a reference to a bugzilla entry. Plead if necessary ;-). Fixed since the last update: - [EliZ] readline/colors.c build failure Caused by S_IXGRP and S_IXOTH not being defined on MinGW. - [EliZ] configure warning when checking for pthread-config Cheers! -- Joel