From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: Brian.Inglis@SystematicSw.ab.ca, purplearmadillo77@proton.me
Subject: Re: ncurses-demo-6.3-1.20220416 not displaying any output
Date: Fri, 21 Oct 2022 15:11:09 -0600 [thread overview]
Message-ID: <01f707dc-83c2-dbfa-3e9a-f716e755e269@SystematicSw.ab.ca> (raw)
In-Reply-To: <OBTqDeb8soLhw7MLalvYaUkrvPB-ki8wr7kNBm62-6eVS2F4wKWMJcvUgZmWxaKU8Vq79kpxyniuE6ze7WIYwcS5UbIp34Ln7ZkV7v8o-SU=@proton.me>
On Fri, 21 Oct 2022 18:49:28 +0000, William Hu wrote:
> When trying to run the pre-built examples in the ncurses-demo-6.3-1.20220416
> package, nothing happens - the bash prompt simply scrolls to the next line. This
> happens for all the example programs, not just one.
> However, if I compile the ncurses examples from source locally on my machine
> with Cygwin, they run normally through a Cygwin prompt. Additionally, it
> seems the previous version (6.1-1.20190727) works fine too, so this seems
> like a bug in the latest version. I’m running Cygwin on 64-bit Windows 10 -
> let me know if you need more info.
Works fine for me with all test packages upgraded to the same version and either
shell restarted or DLLs rebased by setup.
Please check that libncursesw10 has also been upgraded to the same version
6.3-1.20220416 e.g.
$ grep ncurses /etc/setup/installed.db
libncursesw10 libncursesw10-6.3-1.20220416.tar.bz2 0
ncurses-demo ncurses-demo-6.3-1.20220416.tar.bz2 1
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2022-10-21 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 18:49 William Hu
2022-10-21 21:11 ` Brian Inglis [this message]
2022-10-22 17:58 ` William Hu
2022-10-22 22:41 ` Brian Inglis
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=01f707dc-83c2-dbfa-3e9a-f716e755e269@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=purplearmadillo77@proton.me \
/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).