From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: William Hu <purplearmadillo77@proton.me>,
Brian.Inglis@SystematicSw.ab.ca
Subject: Re: ncurses-demo-6.3-1.20220416 not displaying any output
Date: Sat, 22 Oct 2022 16:41:18 -0600 [thread overview]
Message-ID: <aee6be55-90fb-88e0-9293-0c3aa3586f7e@SystematicSw.ab.ca> (raw)
In-Reply-To: <z0_V4F5-8Tsuw9LAL_vwTPS1a1nOKAwBm1Z-qVBm_ssdLST8mXE4vNkjHPECTx5zZ8ivT9_E8T_8pBT5KoHdAagkxusrA7PHEToCHXITH2E=@proton.me>
On 2022-10-22 11:58, William Hu wrote:
>> 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
> Yep, that was the problem! Thank you!
> I think it might be more informative to either produce a warning about
> incompatible library versions rather than just silently exiting or requiring
> a certain minimum version of the library with the demos (not sure if that's
> possible with cygport).
I think that's a long standing limitation installing test packages - test
versions of dependencies are not handled automatically by setup - you also have
to manually choose the test versions of any related packages you are installing.
I normally just pick the root of any package I want to test e.g. ncurses and
select the same test versions of all binaries to install to avoid these issues.
--
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
prev parent reply other threads:[~2022-10-22 22:41 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
2022-10-22 17:58 ` William Hu
2022-10-22 22:41 ` Brian Inglis [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=aee6be55-90fb-88e0-9293-0c3aa3586f7e@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).