Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: GDB 9.1 release -- 2020-01-02 update
Date: Thu, 02 Jan 2020 11:16:00 -0000	[thread overview]
Message-ID: <20200102111623.GF5147@adacore.com> (raw)

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


             reply	other threads:[~2020-01-02 11:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 11:16 Joel Brobecker [this message]
2020-01-02 14:19 ` Joel Brobecker
2020-01-02 14:33   ` Eli Zaretskii
2020-01-08  0:34 ` Christian Biesinger via gdb-patches
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=20200102111623.GF5147@adacore.com \
    --to=brobecker@adacore.com \
    --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