ASSP port testing, not getting all perl mods to work

[Scott Haneda]

I am telling ASSP where the new perl is, this issue is that some  
modules, only three of 15 or more, are being looked for in the wrong  
spot.

I do not know if I should solve this in the port, by editing the  
source of the app, or if there is some other way.  I actually hope  
there is some other way, as there should be no reason why I need to  
modify the source other than to change the perl path at the top of a  
few files.

On Jan 21, 2009, at 5:13 PM, Frank J. R. Hanstick wrote:

> Hello,
> 	It sounds like opt/local is not the first location the path  
> environment looks for perl.  This is a problem when several versions  
> of a program exists because unless a prefix is supplied, the default  
> program will always be found in the order of the pathname (first  
> detected).  If perl exists in /opt/local/bin and /usr/bin and the  
> path is in the order of /usr/bin:/opt/local/bin, then without a  
> prefix, /usr/bin will always be the perl used and visa versa if path  
> is /opt/local/bin:/usr/bin.  I ran into the same problem with gcc  
> located in two different locations.
> Frank

--
Scott