From: Achim Gratz <Stromeko@Nexgo.DE>
To: cygwin@cygwin.com
Subject: Re: How can I completely remove Perl 5.22?
Date: Wed, 28 Oct 2015 01:58:00 -0000 [thread overview]
Message-ID: <n0oeqh$q9c$1@ger.gmane.org> (raw)
In-Reply-To: <CAK-n8j6WU+TdV3n_gc-yyBGc_DuXx9NsUsgqVCPpxS29HCi=sA@mail.gmail.com>
Am 27.10.2015 um 18:49 schrieb Jim Reisert AD1C:
> I am having some problems trying to make ActiveState Perl and Cygwin
> Perl 5.22 co-exist.
If they did so in the past, I see no reason why they shouldn't continue
to do so.
> I currently have a Perl program that uses the Tk
> library, which I am unable to compile using the ActiveState PDK. I am
> pretty sure it was working before I upgraded Cygwin Perl to version
> 5.22. My current thinking is to backtrack to Cygwin Perl 5.14 and see
> if I can make the two co-habitate again.
I would guess that is merely a temporal coincidence.
> Other than un-installing Cygwin Perl, how can I ensure that all CPAN
> and/or compiled libraries/modules are also removed (most likely in my
> Cygwin home directory)?
Unless you've actively subverted it, Perl knows to keep it's stuff
separate from other versions of Perl that may happen to be installed on
the same machine.
You may have an issue with the search order in PATH, though.
> I realize that parts of Perl are needed for
> the Cygwin base install.
No, not yet.
> These are the Cygwin packages that I have installed, that have the
> word "perl" in them:
>
> * perl
> * perl_autorebase
> * perl_base
None of these packages install anything into your home directory.
--
Achim.
(on the road :-)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-10-27 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 0:34 Jim Reisert AD1C
2015-10-28 1:58 ` Achim Gratz [this message]
2015-10-28 18:55 ` Jim Reisert AD1C
2015-10-28 20:38 ` Csaba Raduly
2015-10-29 7:43 ` Jim Reisert AD1C
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='n0oeqh$q9c$1@ger.gmane.org' \
--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).