Installation Support for ActivePerl

Installation Problems, Installer content, and FAQs for ActivePerl

Release Notes for 5.24.2.2403

Due to a problem on the main docs site, the 2402 version of the Release Notes is still the latest available.

You can see the latest version in the documentation inside the ActivePerl 2403 version. For those who can't install it, here is the list of changes between 2402 and 2403:
-----------------------------------------------------------------------

ActivePerl 5.24 Change Log

For the latest information on ActivePerl, please see:

http://www.ActiveState.com/ActivePerl/

Build 2403, August 2017

Build 2403 is based on Perl 5.24.2 plus additional selected changes.

Known Issues in recent releases

This posting will track known issues with the current set of Community Edition releases.

- perdoc errors On Windows
Versions affected
5.24.1.2402 and 5.22.3.2204 (Versions using perldoc v3.27)
Components affected: perldoc
Symptoms: perdoc errors with "invalid argument: -R"
Workaround: perldoc -T (document) | more
Bug Status: Core Perl bug
Fix Availability: Fix expected in the next ActiveState releases for 5.24 and 5.22.

- MicroSoft Compilers are incompatible -
Versions affected:
All 5.18, 5.20, 5.22, 5.24

./perl/bin/perl: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./perl/bin/perl)

Can't install the latest Perl on Oracle Unbreakable Linux

cd ActivePerl-5.20.1.2000-x86_64-linux-glibc-2.15-298557
[xxx ActivePerl-5.20.1.2000-x86_64-linux-glibc-2.15-298557]$ ./perl/bin/perl
./perl/bin/perl: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./perl/bin/perl)

At the moment have installed libc 2.12 and yum update tells me that it is the latest version available.

Can't find libc 2.14 in the repos. Could somebody tell where to get it?

Upgrading while keeping all your settings/modules intact

I discovered that my current AS perl, 5.12, is no longer ppm'able [without a business license] so I'm upgrading to 5.16. I'm worried about how that 'upgrade' should/will go. right now perl is installed in c:\perl64. Can I just install the new 5.16 in the same directory and will it basically leave my installed modules and other such along [perhaps needing a big update via ppm, but still there]? Or will I run into problems?

"Perl Command Line Interpreter has stopped working" when running PPM.

Can't get the PPM GUI to run. This is on Win 7 64-bit. Tried reinstalling 5.16.2 64-bit, with the same result. PPM command line seems to work. Just the GUI won't run. Tried 5.16.2 x86 and this launches the GUI fine.

The following is in the event log:
Faulting application name: perl.exe, version: 5.16.2.1602, time stamp: 0x50d17d90
Faulting module name: ole32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c92c
Exception code: 0xc0000005
Fault offset: 0x0000000000036b3b
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11

Having a problem? Check here first:

Frequently encountered problems may have an FAQ available.

http://community.activestate.com/faq-list?tid=50

ActivePerl 5.26.1 32bit version for 64 bit Windows

Hi,

Need to download ActivePerl 5.26.1 32bit version for 64 bit Windows (Windows 2012 r2 server on Azure cloud).
Could someone help me to get the link?

Thanks,
Venkatesh Kanale

Does 5.26.1.2601 work OK with 64 bit Windows 7

Just wanted to check as I dont want to migrate to Windows 10

Upgraded Perl and now LWP does not work ?

A simple one line program fails on a Use LWP command

Amongst errors are Attempt to load List/Util.pm aborted

Any help appreciated

32bit Release of 5.24.1 has been removed

Hi,
we are using the releases from ActivePerl to build gvim packages with the perl interpreter linked in at https://github.com/vim/vim-win32-installer

However, now that the 5.24.1 32bit package has been removed, the build fails, because the perl package cannot be installed anymore. What was the reason for that? It looks like there is no 32bit release available anymore, looking at http://downloads.activestate.com/ActivePerl/releases/

related issue: https://github.com/vim/vim-win32-installer/issues/60

Thanks for feedback.