From: Eli Zaretskii <eliz@gnu.org>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: Building GDB 15.0.91 on MinGW: Problem with TUI
Date: Fri, 07 Jun 2024 16:48:31 +0300 [thread overview]
Message-ID: <861q58g8y8.fsf@gnu.org> (raw)
In-Reply-To: <599928735.5136862.1717766505896@mail.yahoo.com> (message from Hannes Domani on Fri, 7 Jun 2024 13:21:45 +0000 (UTC))
> Date: Fri, 7 Jun 2024 13:21:45 +0000 (UTC)
> From: Hannes Domani <ssbssa@yahoo.de>
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>
> Isn't that the same as this issue?:
> https://github.com/msys2/MINGW-packages/issues/10434
>
> If yes, it should be fixed with ncurses-6.4-20230211 or newer.
Right, thanks. I need to upgrade my ncurses, I guess.
prev parent reply other threads:[~2024-06-07 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 15:59 GDB 15.0.91 available for testing Joel Brobecker
2024-06-06 20:16 ` Building GDB 15.0.91 on MinGW: CPPFLAGS Eli Zaretskii
2024-06-07 12:21 ` Building GDB 15.0.91 on MinGW: CPPFLAGS and libctf Eli Zaretskii
[not found] ` <87r0d8k0gc.fsf@tromey.com>
2024-06-07 19:56 ` Eli Zaretskii
2024-06-07 21:39 ` Tom Tromey
2024-06-08 6:10 ` Eli Zaretskii
2024-06-08 7:54 ` Eli Zaretskii
2024-06-06 20:20 ` Building GDB 15.0.91 on MinGW: gcore.c Eli Zaretskii
[not found] ` <87msnwk0du.fsf@tromey.com>
2024-06-08 7:25 ` Eli Zaretskii
2024-06-07 12:27 ` Building GDB 15.0.91 on MinGW: ui_out_emit_type<ui_out_type_tuple>::m_uiout Eli Zaretskii
[not found] ` <87ikykk07l.fsf@tromey.com>
2024-06-07 19:57 ` Eli Zaretskii
2024-06-07 12:34 ` Building GDB 15.0.91 on MinGW: libctf.la Eli Zaretskii
2024-06-08 7:56 ` Eli Zaretskii
2024-06-07 13:13 ` Building GDB 15.0.91 on MinGW: Problem with TUI Eli Zaretskii
[not found] ` <599928735.5136862.1717766505896@mail.yahoo.com>
2024-06-07 13:48 ` Eli Zaretskii [this message]
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=861q58g8y8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).