Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #75637

Activestate Perl Download 64 12

Show all headers | View raw

We specialize in stable, secure, and easy-to-deploy Perl environments. Unlike other Perl distributions such as Strawberry Perl or perlbrew, our universal package manager, the State Tool, replaces Comprehensive Perl Archive Network (CPAN) and Perl Package Manager (PPM), and allows you to build runtimes with CPAN modules from source code (including linked C libraries), reducing your exposure to vulnerabilities and eliminate the need for a local compiler/build environment.



activestate perl download 64 12

DOWNLOAD https://1ermapptincba.blogspot.com/?download=2wWq3Q 






In the meanwhile you can fix your project from the command line by updating your package to a working version by using these commands (make sure you cd into the folder that has the activestate.yaml in it first):


I have to agree with the above comments, the move away from ppm has been a total disaster in my opinion. Moving scripts between servers used to be simple, install perl, add the necessary modules and your up and running.


I have just successfully added the Spreadsheet::Read module to my 5.36.1. installation using the command state install Spreadsheet-Read. I confirmed it can be located by running the command perl -e "Spreadsheet::Read".


It has been well over a decade since I have used ActiveState perl. To the best of my memory, I left it because of problems/limitations with ppm. For most of this period, Strawberry perl filled the void though other distributions filled the gap before it came into existence.


With the demise uncertainty of the future of Strawberry perl post 5.32, I am considering giving it a try again. A quick read indicates that ppm has been replaced with the State Tool, a new package manager.


I had read that you could create an ActiveState perl build without creating an ActiveState ID. I could not, at least as far as I could tell. Instead of creating a new ID, I linked it to my GitHUB ID.


Your best bet is to install the Homebrew package managerin the macOS Terminal application (afterinstalling its requirements),and then issue the command brew install perl. This will install the latestversion of Perl, as well as give you instructions for making sure thatinstalled Perl modules stay that way across updates by Homebrew.


To install your own on Linux, you cango the ActiveState routeas above, or also use theHomebrew package manager. There areseveral requirements to install first,and then you canfollow the directions for installing Homebrew and issuethe command brew install perl.






The installed software had inserted into the head of my PATH and also inserted an extra ; after its variables. latexmk seems to have a problem parsing the path to find perl.exe if an empty variable is provided, even though perl.exe was still on my PATH and I could call it from the command line.


see

 -install-mingw>> install MinGW

>> Submitted by troyt on Wed, 01/28/2009 - 17:06.

>> Tags: activeperldmakegccMinGWperlppmwindows

>>

>> Here's a really cool development for ActivePerl

>> users on Windows. MinGW is now available from the

>> ActiveState PPM repository:

>>

>> C:\>ppm install MinGW

>>

>> This installs the MinGW tools (gcc, dlltool, ar, etc.)

>> and dmake in ActivePerl's 'site/bin' directory.However, I have now migrated to Windows 32 bits ActiveState Perl 5.12,

and the MinGW package seems to have disappeared !C:\>ppm install MinGW

ppm install failed: Can't find any package that provides MinGWWhat a lovely package "MinGW" was for Windows 32 bits ActiveState Perl

5.10, I hope it will be available soon for Windows 32 bits ActiveState

Perl 5.12 !!!(...and, while we're on the subject, if possible, also for Windows 64

bits ActiveState Perl 5.12, too, but I think that it would be

difficult to find a 64 bit version of MinGW ... )




As Ben said, the ppm repo for 5.12 isn't fully stocked yet.

In the meantime, if you've still got the 5.10 installation sitting

there, you can use its MinGW and dmake with 5.12. It's just a matter

of adding the perl-5.10/site/bin folder to the *end* of the path.Or you can grab and install MinGW and dmake yourself - without using

ppm. (I think 'ppm' makes it a bit simpler, but.)


You'll get MinGW64 easy enough at -w64.sourceforge.net/ -

though, as I write this, it seems that the site is undergoing an

upgrade.Unfortunately, mingw64 won't work straight out of the box with x64

ActivePerl. Coincidentally, I've been hacking at this today. Having

got everything to the stage where extensions would build, pass their

tests, and install just fine, I then found that there can be weird

runtime failures when DynaLoader tries to load the extension's dll.

(Only seems to affect some extensions - and even then only under

certain conditions ... I really can't yet make much sense of what's

happening.)In short, for the moment at least, you'd be better off grabbing the

freely available "Microsoft Platform SDK for Windows Server 2003 R2"

compiler and using it with the x64 ActivePerl builds (irrespective of

which version of Windows 64 you're running). That's the same compiler

as was used to build the x64 ActiveState perls, and it therefore works

very well with those builds.Cheers,

Rob




> though, as I write this, it seems that the site is undergoing an

> upgrade.

>

> Unfortunately, mingw64 won't work straight out of the box with x64

> ActivePerl. Coincidentally, I've been hacking at this today. Having

> got everything to the stage where extensions would build, pass their

> tests, and install just fine, I then found that there can be weird

> runtime failures when DynaLoader tries to load the extension's dll.

> (Only seems to affect some extensions - and even then only under

> certain conditions ... I really can't yet make much sense of what's

> happening.)

>

> In short, for the moment at least, you'd be better off grabbing the

> freely available "Microsoft Platform SDK for Windows Server 2003 R2"

> compiler and using it with the x64 ActivePerl builds (irrespective of

> which version of Windows 64 you're running). That's the same compiler

> as was used to build the x64 ActiveState perls, and it therefore works

> very well with those builds.


You are mixing 32-bit ("x86") and 64-bit ("x64") code. You can't do

that. They need to match. If I understood you correctly, your perl is

64-bits, so you need to compile your modules in 64-bit mode, too.hp




Unless you have a good reason not to, I'd always download the English

versions. I've no idea if it is the case here, but in the past some MS

products have had language-specific versions which were missing

features.The English version of VC9 can be downloaded from

 . This isn't the latest

version, but that isn't important: what matters is that it matches the

version used to build your Perl, especially with recent MS compilers

which have a nasty habit of introducing incompatible versions of libc

all the time. I don't know which compiler AS use for their 64bit builds:

I thought it was VC7, but I don't have a 64bit Win32 machine on hand to

check. The free download of VC7 was called 'Visual C++ 2003 Express

Edition', and may or may not still be available; search microsoft.com.FWIW, all of this mess is why I gave up on ActivePerl a while ago. I'd

recommend getting

 -perl-5.12.0.1-64bit-v2.msi

which includes the correct compiler as part of the install.Ben




> version, but that isn't important: what matters is that it matches the

> version used to build your Perl, especially with recent MS compilers

> which have a nasty habit of introducing incompatible versions of libc

> all the time. I don't know which compiler AS use for their 64bit builds:

> I thought it was VC7, but I don't have a 64bit Win32 machine on hand to

> check. The free download of VC7 was called 'Visual C++ 2003 Express

> Edition', and may or may not still be available; search microsoft.com.

>

> FWIW, all of this mess is why I gave up on ActivePerl a while ago. I'd

> recommend getting

> -perl-5.12.0.1-64bit-v2.msi

> which includes the correct compiler as part of the install.


What do you mean by "Can Perl be written"? Neither Perl code nor the

perl interpreter need to be specially "written" for RISC processors. The

perl interpreter is written in reasonably portable C and compiles fine

on RISC processors (which aren't that similar, btw: A SPARC processor is

quite different from an Alpha).


Perl may be copied only under the terms of either the Artistic License

or the

GNU General Public License, which may be found in the Perl 5 source

kit.Complete documentation for Perl, including FAQ lists, should be found

on

this system using "man perl" or "perldoc perl". If you have access to

the

Internet, point your browser at , the Perl Home

Page.C:\Users\CK\Documents\PerlModules\Text-CSV_XS\Text-CSV_XS-0.73>perl

Makefile.PL


I have been trying to use the Perl Scripting node in KNIME 3.6.1 for windows (Windows server 16) though I keep running into this problem. I have been able to find three different Perl installations on this system (or at least three different occurrences of perl.exe):


Extensive online documentation is included with Perl itself. You can read thedocumentation with the perldoc command, as in perldocdocument_name. You should start with the perl document and the perlfaqdocument. For information on other ways of accessing the Perl documentation(including HTML versions of this documentation), see Wherecan I get documentation on ActivePerl?.


For general perl, two books to consider are Programming Perl, 3rdEdition, by Larry Wall, Tom Christiansen and Randal L. Schwartz (O'Reilly &Associates, 1996) and Learning Perl, 3rd Edition, by Randal L. Schwartz (O'Reilly& Associates, 1993). These are referred to by Perl enthusiasts as the Camelbook and the Llama book, respectively.


If you run Perl at the command prompt, the script will be executed by thefirst Perl.exe it encounters in the list of paths in the PATH environmentvariable. To ensure the script is executed by the Perl build you want it to beexecuted by, you can specify the complete path to the Perl.exe you want to use.(typing perl -v at the command prompt will tell you which versionof Perl is currently first in your PATH).

 0aad45d008

Back to comp.lang.javascript | Previous | Next | Find similar | Unroll thread

Thread

Activestate Perl Download 64 12 Parmenides Mcloven <mclovenparmenides@gmail.com> - 2023-12-26 04:33 -0800

csiph-web