From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: updating Perl problem
Date: Fri, 20 Mar 2020 14:06:53 +0100 [thread overview]
Message-ID: <875zezdvki.fsf@Otto.invalid> (raw)
In-Reply-To: <6806e424-a946-a9fd-31b9-af5456460c13@gmail.com> (Marco Atzeri via Cygwin's message of "Fri, 20 Mar 2020 08:37:38 +0100")
Marco Atzeri via Cygwin writes:
>>>> Compiling perl-Pango-1.227-3.x86_64
> Pre-requisites not found:
> Can't locate ExtUtils/Depends.pm in @INC (you may need to install the
> ExtUtils::Depends module)
Does that also fail with
perl -MExtUtils::Depends < /dev/null && echo OK || echo Fail
and if yes, is the file readable for the euid you are compiling under?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
prev parent reply other threads:[~2020-03-20 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 7:37 Marco Atzeri
2020-03-20 13:06 ` ASSI [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=875zezdvki.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).