From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Building the 7.8.90 pretest on MinGW
Date: Mon, 19 Jan 2015 17:48:00 -0000 [thread overview]
Message-ID: <83lhkyy84l.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22TWRH+EBxr6i_kKX2NuVy9Gczo3v=FUWQGOFZqD9SpELA@mail.gmail.com>
> Date: Thu, 15 Jan 2015 11:49:06 -0800
> From: Doug Evans <dje@google.com>
> Cc: gdb-patches <gdb-patches@sourceware.org>
>
> On Thu, Jan 15, 2015 at 8:07 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > I've built the pretest using MinGW32. I found 2 issues: one with
> > gnulib's time.h (reported to the gnulib list), the other with the
> > recent changes in tui/. Specifically, starting "gdb -tui" fails with
> > this error message:
> >
> > Cannot enable the TUI: error opening terminal [TERM=<unset>]
> >
> > This happens because the recent additions to tui.c make assumptions
> > about the curses library that don't hold for the MinGW port of
> > ncurses, e.g. that $TERM must be set.
> >
> > The patch below fixes this for me. OK to install it (master and
> > branch)?
> >
> > 2015-01-15 Eli Zaretskii <eliz@gnu.org>
> >
> > * gdb/tui/tui.c (tui_enable) [__MINGW32__]: If the call to 'newterm'
> > fails with the 1st arg NULL, try again with "unknown". Don't test
> > the "cup" capability: it isn't supported by the Windows port of
> > ncurses, but the Windows console driver is still capable of
> > supporting TUI.
>
> Ok by me.
Thanks. I'd like to hear from Pedro as well, as the changes which
caused this were committed by him.
next prev parent reply other threads:[~2015-01-19 17:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.20150113122445.36DDE48E8A@joel.gnat.com>
2015-01-15 16:07 ` Eli Zaretskii
2015-01-15 19:49 ` Doug Evans
2015-01-19 17:48 ` Eli Zaretskii [this message]
2015-01-22 11:05 ` Pedro Alves
2015-01-22 16:09 ` Eli Zaretskii
2015-01-22 17:04 ` Pedro Alves
2015-01-22 17:27 ` Eli Zaretskii
2015-01-22 17:46 ` Pedro Alves
2015-01-22 18:30 ` Eli Zaretskii
2015-01-16 8:49 ` Eli Zaretskii
2015-01-20 18:27 ` Joel Brobecker
2015-01-20 18:36 ` Eli Zaretskii
2015-01-20 19:08 ` 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=83lhkyy84l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.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