From owner-freebsd-questions Sat Feb 27 11:53:52 1999 Delivered-To: freebsd-questions@freebsd.org Received: from red.juniper.net (red.juniper.net [208.197.169.254]) by hub.freebsd.org (Postfix) with ESMTP id 205611516D for ; Sat, 27 Feb 1999 11:53:50 -0800 (PST) (envelope-from pst@juniper.net) Received: from weaver.juniper.net (weaver.juniper.net [208.197.169.243]) by red.juniper.net (8.8.8/8.8.5) with ESMTP id LAA27078 for ; Sat, 27 Feb 1999 11:53:34 -0800 (PST) Received: (from pst@localhost) by weaver.juniper.net (8.8.5/8.7.3) id LAA02577 for questions@freebsd.org; Sat, 27 Feb 1999 11:53:32 -0800 (PST) Date: Sat, 27 Feb 1999 11:53:32 -0800 (PST) From: Paul Traina Message-Id: <199902271953.LAA02577@weaver.juniper.net> To: questions@freebsd.org Subject: perl5: Can't find 'boot_' symbol in /usr/local/lib/perl5/5.000502/i386-freebsd/auto/... Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just built perl5.00502 on a server running freebsd 2.2.8. When I run it on a client running 2.2.5 (bleah), perl chokes any time I try to use an autoloading module, for instance: echo "use Socket;" | /usr/local/bin/perl Can't find 'boot_Socket' symbol in /usr/local/lib/perl5/5.00502/i386-freebsd/auto/Socket/Socket.so at - line 1 BEGIN failed--compilation aborted at - line 1. I even copied over a new libc.so.3.1 to the 2.2.5 client and ldconfig'ed just for grins, no luck, so then I whipped over a 2.2.8 kernel and booted that too, no luck. Suggestions? Has anyone seen this interaction when running a new perl on old machines? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message