![]() ![]() I believe the original underlying issue was something to do with different PATH variables for 32-bit and 64-bit environments and possibly some internal Windows redirection that takes place automatically. If you had a PowerShell window open before setting the PATH variable, you will need to close it and re-open another instance of PowerShell. That fixed it and entering 'perl -v' into command prompt successfully replies your Perl version. (The directory paths are for the 64 bit edition of Perl, adjust according to your installation) the %PATH% portion is important and ensures your existing settings are kept and not wiped out and overwritten when you set the PATH. So to remedy that I entered this into the command prompt and hit enter: set PATH=C:\Perl64\bin C:\Perl64\site\bin %PATH% The official repository is hosted by ActiveState. ActivePerl installs modules using its own format called PPM (Perl Package Manager). This change affects: ActivePerl 5.26 and ActivePerl 5. You can experience the future direction of PPM today by signing up for a free account, and getting started creating your own custom Perl distributions. This change affects: ActivePerl 5.26 and ActivePerl 5.28 Community Edition (CE) Window 10 users only Pleas Effective today, ActiveState has replaced our Windows MSI installer for ActivePerl with a more modern version. I think Strawberry Perl also comes with a few modules that let you install PPMs (Perl Package Manager files). With the release of ActivePerl 5.28, PPM is no longer supportedHowever, its functionality is being replaced by the ActiveState Platform and the State Tool. I tried installing 'Microsoft Visual C++ 2008 x86 and 圆4 redistributable setup' files as suggested by a few places but it still did not resolve the issue, until I tried some of the suggestions in this thread.Īt the command prompt I entered: set PATHĪnd surprisingly it did not list the Perl directories as being included in the PATH variables. The MinGW distribution comes with gcc, make, ld and other tools to help you build modules. I remember selecting the option during installation to add the Perl directory to the system PATH environment, and after checking the system properties, it was indeed showing in the system PATH. 'perl' is not recognized as an internal or external command, operable I was getting a similar error after installing ActiveState Perl on Windows 8 圆4 bit edition and trying to invoke 'perl' at the command line.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |