I've always compiled it on the machine with the compiler, the tar'd
the build directory, moved it to the new machine, the perform the make
install on the target machine. Directory structure, perl version, ars
install dir, etc. are all the same between the machines I maintain.
Axton Grams
On Jan
What I've done to keep this simple is to just build perl as I would want
it on all server with all of the modules, etc. Then tar up the entire
perl folder and extract it on all of the other servers. Also add
depencies like the arapi folder, other api folders (if needed) into the
same directory st
On Jan 31, 2008, at 6:21 PM, White, Linn wrote:
Is this the blib directory that is created after I do a 'make' in my
current directory?
Yes
Also, I'm having trouble tracking down a C compiler on any of our
aix machines. Is there any place I can find a pre-compiled version
for AIX?
Is this the blib directory that is created after I do a 'make' in my current
directory?
Also, I'm having trouble tracking down a C compiler on any of our aix machines.
Is there any place I can find a pre-compiled version for AIX?
-Original Message-
From: [EMAIL PROTECTED] on behalf of
You don't even have to 'install' it. You can copy the blib directory
and the, at the top of your script place
use lib '/path/to/blib';
which will allow perl to find the ARS module
jeff
On Jan 31, 2008, at 2:24 PM, White, Linn wrote:
I am currently working on getting ARSPerl installed on one
I am currently working on getting ARSPerl installed on one of our lab servers,
and will need to move it to multiple servers once it's tested and compiled.
The issue is that the servers I will be moving to do not have any compilers on
them, so I will have to copy the files over. What files are
6 matches
Mail list logo
