On Monday, January 13, 2003, at 04:42 PM, Morbus Iff wrote:
> khsmith% sudo perl -MCPAN -eshellAs a matter of fact, I'm having similar problems, with significant differences. Lemme get some obligatories out of the way here...
> dyld: perl Undefined symbols:
> _Perl_sv_2pv
> _perl_get_sv
> Trace/BPT trap
As per the article, under the "Preparation" portion:
If, after the installation, you get warnings about missing symbols, you
probably have an old version of Perl (or parts of one) in /Library/Perl.
These undefined symbols existed in pre-5.8.0 versions. For more
information on this issue, check out perldelta.
with a link to:
http://dev.perl.org/perl5/news/2002/07/18/580ann/ perldelta.html#mac%20os%20x%20dyld%20undefined%20symbols
500 MHz PowerBook G4, 20Gb HD total (about 2.3Gb free), 512Mb memory, running OS 10.2.3, and with a hand-compiled Perl 5.8.0 and Apple's X11 beta, blah blah blah...
I have a very similar problem with Perl doing untoward crashy things because of undefined symbols. However, I can run the CPAN just fine. I'm having my problems with, among other things, GIMP, which has some Perl calls in it which crash *consistently*.
I tried deleting the libperl.dyld, I tried renaming it, I tried deleting every bundle in /System/Library/Perl/*.
As a last resort, I tried "sudo mv /System/Library/Perl /System/Library/Perl-Old" and redid the "sudo make install" to create a *new* Perl directory. Same problem all over again. Bleh.
Could the problem have anything to do with the dyld search paths, which the make process griped about for no fathomable reason?
--David http://skipjack.bluecrab.org/~dwood
"After all, we can't have too many meta-stable personality constructs
gallivanting around the universe in Pfhor attack ships, can we?"
--Durandal, Marathon 2
