From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: curl 7.71.1-1
Date: Tue, 11 Aug 2020 07:15:13 +0200 [thread overview]
Message-ID: <87pn7xrcf2.fsf@Otto.invalid> (raw)
In-Reply-To: <4f1d6241-c86b-f2f9-7b49-a9f5b998b0eb@SystematicSw.ab.ca> (Brian Inglis's message of "Sun, 9 Aug 2020 15:48:33 -0600")
Brian Inglis writes:
> - it complains that perl(DBD::SQLite) perl(IO::Pty) are not installed - how do
> these and your other perl module dependencies map to Cygwin packages?
> I also mean that in general - how can I map a perl module to a perl package and
> vice versa - for future info?
You go look up the distribution that provides this mocule on MetaCPAN
and then install perl-<distrib-name>. Eventually though, such these
dependencies should be listed in the cygport file with their Cygwin
package names as BUILD_REQUIRES.
Regards
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
next prev parent reply other threads:[~2020-08-11 5:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 2:34 Brian Inglis
2020-07-20 17:58 ` ASSI
2020-08-10 18:16 ` Brian Inglis
2020-08-10 20:11 ` Marco Atzeri
[not found] ` <CA+kUOa=-AJxr_2TaZoNerOquMGR8FCzi7hg3DyuvntuQqpAVOg@mail.gmail.com>
2020-08-09 18:28 ` Adam Dinwoodie
2020-08-09 21:48 ` Brian Inglis
2020-08-10 3:32 ` Brian Inglis
2020-08-10 14:52 ` Ken Brown
2020-08-10 17:33 ` Brian Inglis
2020-08-10 19:14 ` Ken Brown
2020-08-10 20:52 ` Adam Dinwoodie
2020-08-11 1:27 ` Brian Inglis
2020-08-11 11:13 ` Ken Brown
2020-08-11 11:27 ` Adam Dinwoodie
2020-08-11 22:00 ` Brian Inglis
2020-08-14 18:19 ` Brian Inglis
2020-08-15 22:44 ` [ANNOUNCEMENT] Updated: curl 7.71.1-2 Brian Inglis
2020-08-16 19:28 ` Adam Dinwoodie
2020-08-11 5:15 ` ASSI [this message]
2020-08-11 5:55 ` [ANNOUNCEMENT] Updated: curl 7.71.1-1 Brian Inglis
2020-08-11 15:03 ` ASSI
2020-08-11 22:00 ` 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=87pn7xrcf2.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--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).