I've been lurking, but I have some experience building and rebuilding 
other packages.  What I also look at is the timestamp on the files to 
see if the installation process is putting everything out there, or 
there was some old stuff hanging around.  In particular:

ls -l `which <newly installed executable>`

Just lets me know where the install is dropping things.

At 9:59AM -0700 9/23/02, Brian McNett wrote:
>On Monday, September 23, 2002, at 09:44  AM, Jerry LeVan wrote:
>
>>  Hmm, you might try retargeting the build to something like /usr/local.
>>  I have perl 5.6 and 5.8 coexisting. I have built Perl/Tk in 5.8 and it seems
>>  to be working fine.
>
>Well, that is what I *thought* I'd done:
>
>bash-2.05a-bmcnett /usr/local/bin$ ls -l perl
>-rwxr-xr-x  3 root  wheel  21560 Sep 22 20:14 perl
>
>so, Perl exists in that location... but:
>
>bash-2.05a-bmcnett /usr/local/bin$ which perl
>/usr/bin/perl
>
>bash-2.05a-bmcnett /usr/local/bin$ /usr/bin/perl -v
>
>This is perl, v5.8.0 built for darwin
>
>and...
>
>bash-2.05a-bmcnett /usr/local/bin$ /usr/local/bin/perl -v
>
>This is perl, v5.8.0 built for darwin
>
>OUCH.
>
>--B

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                          +1-703-227-9854
ARIN Research Engineer

Reply via email to