On 11-11-16 12:38 AM, Danny Wong (dannwong) wrote:
Hi all,
I received a custom compiled perl binary version, years ago. The path
location of the perl binary and lib paths are hardcoded. Is there a way for me
to override this path setting, so the custom perl binaries are not looking at
On Wed, 16 Nov 2011 02:25:18 -0500, shawn wilson wrote:
> Yes, it was 5.6.1. I wish I had the perl source code to compile. That
> would be the simplest solution. The perl binaries where provided by a
> vendor and the product only works with the customized version of perl
> they compiled for us. The
t;Danny Wong (dannwong)"
Date: Nov 16, 2011 2:00 AM
Subject: RE: overriding a custom compiled perl binary
To: "shawn wilson"
thanks for the information. Yes, it was 5.6.1. I wish I had the perl source
code to compile. That would be the simplest solution. The perl binaries
where provide
/me grumbles about the reply-to on this list
-- Forwarded message --
From: "shawn wilson"
Date: Nov 16, 2011 1:57 AM
Subject: Re: overriding a custom compiled perl binary
To: "Danny Wong (dannwong)"
Override - no.
Append to - export PERL5LIB (assuming perl
Hi all,
I received a custom compiled perl binary version, years ago. The path
location of the perl binary and lib paths are hardcoded. Is there a way for me
to override this path setting, so the custom perl binaries are not looking at
that specific directory or needs to be in the specifi
