From owner-freebsd-current Sun Sep 10 19:29:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with ESMTP id DC87137B424 for ; Sun, 10 Sep 2000 19:29:10 -0700 (PDT) Received: (from bugs@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id VAA25145 for freebsd-current@freebsd.org; Sun, 10 Sep 2000 21:29:20 -0500 (CDT) From: Mark Hittinger Message-Id: <200009110229.VAA25145@freebsd.netcom.com> Subject: make world libcrypto Undefined symbol "RSA_PKCS1" To: freebsd-current@freebsd.org Date: Sun, 10 Sep 2000 21:29:20 -0500 (CDT) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It may be because of something screwy that I did, I had been cvsup'ing from cvsup3. Saw the note about 3 not having a full crypto mirror so I tried a cvsup from 2 and make world completed, but when running ssh I get this: /usr/libexec/ld-elf.so.1: /usr/lib/libcrypto.so.1: Undefined symbol "RSA_PKCS1" Restoring a libcrypto.so.1 from an earlier backup gets things going again. Just blue skying for a minute here, but I wonder if it might be possible to make a short list of critical utilities that depend on some of these critical libraries. It would be quite helpful to test the libraries with the criticial utilities prior to installing them. How many times have we blown our libc.so and then we are really inconvenienced? This one is not as bad as a libc.so hose though. Something that could invoke a dummy image load of /usr/bin/login against the soon to be installed libc, and if it got undefined symbols, bail on the libc installation. I bet this would save some of us infrequent grief! FYI Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message