/me grumbles about the reply-to on this list ---------- Forwarded message ---------- From: "shawn wilson" <ag4ve...@gmail.com> Date: Nov 16, 2011 1:57 AM Subject: Re: overriding a custom compiled perl binary To: "Danny Wong (dannwong)" <dannw...@cisco.com>
Override - no. Append to - export PERL5LIB (assuming perl 5. Neither of those comments are the real answer you *need* though. I think what you really want is a deep meditation session, then look deep inside yourself and ask yourself 'why not just make my own build'. I don't know that even activestate offers anything that isn't open source now days (I'm sure to get corrected on that). Seriously, grab perlbrew and let it ride. Probably the most annoying part of the process is the five or so minutes you have to wait for it. Ps, I hear strawberry perl is decent on the windows side. On Nov 16, 2011 12:40 AM, "Danny Wong (dannwong)" <dannw...@cisco.com> 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 that specific directory or needs to be in the specific > directory? I know I can ask the person to recompile the perl binary again, > but I'm thinking there is a way to override this and point the execute to a > different path. Any ideas? Thanks. > > Ex. /usr/local/<user>/perl > >
