[MacPorts] #20083: Discrepancy between OSX default PERL and MacPorts

MacPorts noreply at macports.org
Fri Jun 26 09:50:18 PDT 2009


#20083: Discrepancy between OSX default PERL and MacPorts
-------------------------------------+--------------------------------------
 Reporter:  brianberneker@…          |       Owner:  macports-tickets@…                   
     Type:  defect                   |      Status:  new                                  
 Priority:  Normal                   |   Milestone:                                       
Component:  ports                    |     Version:  1.7.1                                
 Keywords:                           |        Port:  PERL                                 
-------------------------------------+--------------------------------------
 I have been developing some tools in PERL using MacPorts to add modules
 etc.  I have had some weird problems with my scripts working fine from the
 command line, but then when I run them from a LaunchDaemon I get include
 errors.

 Upon further investigation, it looks like the LaunchDaemon is running the
 (older) default PERL that comes with Leopard, but the command line is not,
 even as root, which the LaunchDaemon is supposed to do.

 Is there a simple way to set it up so that OSX uses the MacPorts PERL and
 its corresponding includes only, so that I don't have to duplicate all my
 PERL and libraries each time I add a module?

 I only need one instance of PERL, and MacPorts seems to have taken over my
 MAKE command for itself, and I don't know how to migrate stuff over to the
 OSX default PERL interpreter, or switch it, etc.

-- 
Ticket URL: <http://trac.macports.org/ticket/20083>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list