From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: GDB 9.1 release 2019-12-23 update
Date: Mon, 23 Dec 2019 09:30:00 -0000 [thread overview]
Message-ID: <20191223093031.GE11677@adacore.com> (raw)
Hi everyone,
So, as far as I know, the only issues that are still open are
the issues that Eli found with the pre-release.
- [EliZ] readline/colors.c build failure
Caused by S_IXGRP and S_IXOTH not being defined on MinGW.
Patch sent to readline, and should be applied to our local
tree soon.
- [EliZ] configure warning when checking for pthread-config
Problem understood, but EliZ blocked because he doesn't have
the correct auto-tools version. Hopefully building those
from source is an option.
- [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
If we don't get an answer after the end of year holidays,
I suggest we send in a patch, which will likely help move
things along. From Eli's message on bugzilla, we shouldn't
be far from having one.
There might also be an issue with GDB/TUI, but that's less clear
at this stage.
Are there other issues that I may have missed for which we should
wait until we can release GDB 9.1?
Thank you!
--
Joel
next reply other threads:[~2019-12-23 9:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 9:30 Joel Brobecker [this message]
2019-12-23 14:14 ` Eli Zaretskii
2019-12-23 14:32 ` Eli Zaretskii
2019-12-24 3:47 ` Joel Brobecker
2019-12-24 12:24 ` Andrew Burgess
2019-12-24 15:52 ` Eli Zaretskii
2020-01-03 16:21 ` Tom Tromey
2019-12-24 16:21 ` Eli Zaretskii
2019-12-26 22:40 ` Christian Biesinger via gdb-patches
2019-12-27 7:49 ` Eli Zaretskii
2019-12-25 21:36 ` Andrew Burgess
2020-01-02 10:56 ` Joel Brobecker
2020-01-06 22:00 ` Andrew Burgess
2019-12-28 16:22 ` Hannes Domani via gdb-patches
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=20191223093031.GE11677@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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