From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: spk121@yahoo.com, h.c.f.mueller@gmail.com
Subject: Re: guile 3.0.8: readline does not work - patch with also other fixes
Date: Sat, 8 Oct 2022 01:30:38 -0600 [thread overview]
Message-ID: <228dfb7f-3c29-c1b2-71c0-fdc71499aaf0@SystematicSw.ab.ca> (raw)
In-Reply-To: <29ee8089120cd0ba86c2460c0491e00383959759.camel@gmail.com>
Hi folks,
On my system with over 2K Cygwin packages installed, of which over 900
are named lib..., there are over 750 simple cygP-[0-9]+.dll including
cygPV-[0-9]+.dll, over 250 compound version cygPV-M-m.dll, and about 80
with no -, including about 64 semantic versions:
cygicudata56...70.dll
cygicui18n56...70.dll
cygicuio56...70.dll
cygicuuc56...70.dll
cygicule56.dll
cygicule57.dll
cygiculx56.dll
cygiculx57.dll
cygicutest70.dll
cygicutu70.dll
cygperl5_32.dll
cygruby260.dll
about 16 likely current - age ABI versions:
cygcatgets1.dll
cygfreebl3.dll
cygfreeblpriv3.dll
cyghistory7.dll
cygnspr4.dll
cygnss3.dll
cygnssdbm3.dll
cygnssutil3.dll
cygplc4.dll
cygplds4.dll
cygreadline7.dll
cygsmime3.dll
cygsoftokn3.dll
cygssl3.dll
cygusb0.dll
about a half dozen with no versions:
cyggvfscommon.dll
cyggvfsdaemon.dll
cygnativeGLthunk.dll
cygregina.dll
cygtxc_dxtn.dll
cygz.dll
and the one to rule them all:
cygwin1.dll
The intensely curious can download over 170GB compressed tars and scan
the over 12000 binary packages available for DLLs. ;^>
--
La perfection est atteinte,
non pas lorsqu'il n'y a plus rien à ajouter,
mais lorsqu'il n'y a plus rien à retirer.
-- Antoine de Saint-Exupéry
prev parent reply other threads:[~2022-10-08 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 18:06 Hannes Müller
2022-10-04 23:07 ` Mike Gran
2022-10-06 19:13 ` Hannes Müller
2022-10-08 7:30 ` 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=228dfb7f-3c29-c1b2-71c0-fdc71499aaf0@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=h.c.f.mueller@gmail.com \
--cc=spk121@yahoo.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).