public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: missing perl directories
Date: Fri, 22 Jan 2021 00:33:45 -0700	[thread overview]
Message-ID: <d56b5b94-febf-bd4d-ead1-200b900e89a4@SystematicSw.ab.ca> (raw)
In-Reply-To: <ce12be86-779e-41cc-af80-ba0ecb2b210a@www.fastmail.com>

On 2021-01-21 09:09, Anthony Heading wrote:
> Whenever I have a new cygwin setup,  I get an error/warning when trying to install perl modules:
> 
> % cpan install Win32::Symlink
> Loading internal logger. Log::Log4perl recommended for better logging
> [...]
> Use of uninitialized value $what in concatenation (.) or string at /usr/share/perl5/5.30/App/Cpan.pm line 679, <STDIN> line 1.
> Warning: You do not have write permission for Perl library directories.
> 
> I think it is just because the site_perl directories do not exist.
> 
> % perl -V
> Summary of my perl5 (revision 5 version 30 subversion 3) configuration:
> [...]
>    @INC:
>      /usr/local/lib/perl5/site_perl/5.30/x86_64-cygwin-threads
>      /usr/local/share/perl5/site_perl/5.30
>      /usr/lib/perl5/vendor_perl/5.30/x86_64-cygwin-threads
>      /usr/share/perl5/vendor_perl/5.30
>      /usr/lib/perl5/5.30/x86_64-cygwin-threads
>      /usr/share/perl5/5.30
> 
> ls: cannot access '/usr/local/lib/perl5/site_perl/5.30/x86_64-cygwin-threads': No such file or directory
> ls: cannot access '/usr/local/share/perl5/site_perl/5.30': No such file or directory
> 
> If I simply create these empty directories the problem goes away.
> 
> Could the perl package just include these empty directories?

I don't knowingly use perl packages but I have those directories:

$ perl -V | tail -6 | xargs ls -d
/usr/lib/perl5/5.30/x86_64-cygwin-threads 
/usr/local/share/perl5/site_perl/5.30
/usr/lib/perl5/vendor_perl/5.30/x86_64-cygwin-threads      /usr/share/perl5/5.30
/usr/local/lib/perl5/site_perl/5.30/x86_64-cygwin-threads 
/usr/share/perl5/vendor_perl/5.30

either something has not completed correctly, or something is missing in recent 
installations.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  parent reply	other threads:[~2021-01-22  7:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 16:09 Anthony Heading
2021-01-21 16:22 ` Marco Atzeri
2021-01-22  7:33 ` Brian Inglis [this message]
2021-01-22 16:15   ` Anthony Heading
2021-01-22 16:36     ` Marco Atzeri
2021-01-22 17:53       ` Anthony Heading
2021-01-22 19:43         ` Ken Brown
2021-01-22 20:29         ` Achim Gratz
2021-01-22 19:35 ` Achim Gratz
2021-01-22 21:05   ` Anthony Heading
2021-01-23 19:08     ` Achim Gratz
2021-01-24 16:14       ` Anthony Heading

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=d56b5b94-febf-bd4d-ead1-200b900e89a4@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).