With your vendor's or system's perl, you'd normally just enter
perl some_script.pl; however, with ActivePerl, unless you specifically changed policy to make it your system perl, you have to use the full path to ActivePerl. On my system, the full path is
/opt/ActivePerl-5.14/bin/perl
Your path will most likely be different. To use ppm, again you'd do something similar such as:
/opt/ActivePerl-5.14/bin/ppm install Some::Module
| [reply] [d/l] [select] |
Undefined subroutine &My::Builder::Darwin::rel2abs called at inc/My/Bu
+ilder/Darwin.pm line 115.
FROGGS/SDL-2.536.tar.gz
./Build -- NOT OK
Running Build test
Can't test without successful make
Running Build install
Make had returned bad status, install seems impossible
Failed during this command:
FROGGS/SDL-2.536.tar.gz : make NO
And the PPM program has never heard of SDL, although it provides something called "Alien-SDL" which I've installed but don't know what to do with.
EDIT: Well, I tried downloading the package and installing it manually, and that gave the same error about "rel2abs". Somewhat desperate, I edited the Darwin.pm file myself, which felt very very wrong. A quick googling suggested that "File::Spec" was needed, so I added that to the file. Now the testing went fine, and the install didn't seem to have any problems either. Unfortunately neither of the Perl versions acknowledges that I have installed SDL. So maybe it ended up in a third place. | [reply] [d/l] |
It seems a little silly to have two different versions
I have a policy about the Perl installed with the system / OS - do not touch it. Unless my application is being bundled with the OS or needs to run on the bare OS, I install my own version of Perl. This allows my application to dictate the version of Perl, compile options, library / module versions, and so on without needing to be concerned with a patch or upgrade of the OS hosing my application, or conversely, my application hosing the OS.
| [reply] |
| [reply] |