From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [pushed] Rename windows-termcap.c -> stub-termcap.c
Date: Thu, 26 Feb 2015 17:38:00 -0000 [thread overview]
Message-ID: <54EF5A28.2080009@redhat.com> (raw)
In-Reply-To: <83egpc60dc.fsf@gnu.org>
On 02/26/2015 05:36 PM, Eli Zaretskii wrote:
>> From: Pedro Alves <palves@redhat.com>
>> Date: Thu, 26 Feb 2015 17:20:58 +0000
>>
>> Preparation for using this on all hosts.
>>
>> Confirmed that --host=x86_64-w64-mingw32 still builds the stub
>> termcap.
>
> I think we should verify that a non-MinGW host which lacks termcap
> will still work with the stub.
Agreed, I tried that locally (and so did Bernd), but note this patch
does just the rename, doesn't make GDB use the fallback stub on
all hosts yet.
> Readline has a few MinGW-specific
> fragments, at least one of them seems to be related to termcap; if
> some other host doesn't use similar workarounds in Readline, it might
> be subtly broken.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-02-26 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 17:22 Pedro Alves
2015-02-26 17:36 ` Eli Zaretskii
2015-02-26 17:38 ` Pedro Alves [this message]
2015-02-26 17:40 ` Mark Kettenis
2015-02-26 17:45 ` Pedro Alves
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=54EF5A28.2080009@redhat.com \
--to=palves@redhat.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