On Sep 7, 2008, at 11:42 AM, David Green wrote:

Do you have an issue of Perl versions here -- 5.8.6 having been upgraded to 5.8.8? I never solved the issue myself; ultimately I just stayed with the OS X standard or 5.8.8 and removed MacPorts. Would love for some clued in explanations ;)

I can not remember the details of what I was trying but I guess it was less important then having a fully 'aware' Perl installation.

David

Hi David,

As far as I can tell Perl on a Mac pays absolutely no attention the environmental variable PERL5LIB. I have eliminated all PERL5LIB specifications on my machine.

Here are a couple of test scripts that illustrate my point.

Script 1
   [put either shebang line here]

   #!/usr/bin/perl -w
   #!/opt/local/bin/perl -w

   # test1.pl  - Test Perl constructs

   use strict;
   use Date::Format;

Script 2
   [put either shebang line here]

   #!/usr/bin/perl -w
   #!/opt/local/bin/perl -w

   # test2.pl  - Test Perl constructs

   use strict;
   use Crypt::SSLeay;

When I run Script 1, either from Terminal or from BBEdit, nothing happens with the top shebang line (Date::Format is in my /usr/bin/ perl [5.8.6] tree), but I get an error message listing @INC with the bottom shebang line (Date::Format is not in my /opt/local/bin/perl [5.8.8] tree).

Just the opposite situation occurs when I run Script 2, either from Terminal or from BBEdit. I get an error message listing @INC with top bottom shebang line (Crypt::SSLeay is not in my /usr/bin/perl [5.8.6] tree), but nothing happens with the bottom shebang line (Crypt::SSLeay is in my /opt/local/bin/perl [5.8.8] tree).

I have found no way of running a module in one Perl tree with the other version of Perl.

Regards,

Vic

Reply via email to