public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Alexander Voropay <alec@sensi.org>
To: cygwin@cygwin.com
Subject: Re: cygwin mingw crosscompiler / readline bug
Date: Mon, 06 Jan 2020 21:59:00 -0000	[thread overview]
Message-ID: <CAGqcPWDs7Vteed_a5NwgqTt_Fb4sLeUWm4Q7eU1LUuTdphdO3w@mail.gmail.com> (raw)
In-Reply-To: <CAGqcPWC7T_FHmS1+nRgAA56fUoWNOk1LuCqkOqb4FG=Zgkx5Qg@mail.gmail.com>

Auto-answer..he-he...

> I'm trying to compile a standalone Windows-32 console application
> using 'readline' with cygwin's  'i686-w64-mingw32-gcc' crosscompiler.
>
> I have a bug: readline repeates every input line to STDOUT on
> Windows-32 application (running from the CMD.EXE, outside a Cygwin)

'readline' library requires terminal-specific functions like
tputs()/tgetnum() e.t.c.
and should be linked with old-good 'libtermcap' (not provides with Cygwin now)
or with more recent curses library i.e. 'ncurses' or 'pdcurses'.

On the Cygwin's 'i686-w64-mingw32-gcc' crosscompiler 'libreadline' depends
on the 'ncurses' which has special support for Win32 console 'terminal'.
To enable Win32 console support set a TERM environment:

set TERM=#win32console

(yes! with # character)

--
-=AV=-

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2020-01-06 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 14:03 Alexander Voropay
2020-01-06 21:59 ` Alexander Voropay [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=CAGqcPWDs7Vteed_a5NwgqTt_Fb4sLeUWm4Q7eU1LUuTdphdO3w@mail.gmail.com \
    --to=alec@sensi.org \
    --cc=cygwin@cygwin.com \
    /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).