Technically this is bad form to bring an email back on the list after it was off list. But I don't feel either of us meant to bring it off list, and most on this know more than me, so...
I don't know your code base but would be very surprised (and outraged) if a project required a custom core. I could understand some proprietary xs but don't know that that should stop you from running stock perl. Either way, perl5lib or 'use lib' is the easy answer. Also perldoc perlrun may yield other bits of goodness for you. ---------- Forwarded message ---------- From: "Danny Wong (dannwong)" <dannw...@cisco.com> Date: Nov 16, 2011 2:00 AM Subject: RE: overriding a custom compiled perl binary To: "shawn wilson" <ag4ve...@gmail.com> 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 provided by a vendor and the product only works with the customized version of perl they compiled for us. The vendor doesn’t exist any more. *** * ** ** *From:* shawn wilson [mailto:ag4ve...@gmail.com] *Sent:* Tuesday, November 15, 2011 10:57 PM *To:* Danny Wong (dannwong) *Subject:* Re: overriding a custom compiled perl binary**** ** ** 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****
