From owner-freebsd-current Sun Mar 5 13:53:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id D9B6A37BBDB; Sun, 5 Mar 2000 13:53:42 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.13 #1) id 12Riy6-0004iC-00; Sun, 05 Mar 2000 13:53:42 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Kris Kennaway Cc: FreeBSD Current Subject: Re: libcrypto.a - deja vu? References: Message-Id: Date: Sun, 05 Mar 2000 13:53:42 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> cc -fpic -DPIC -O -pipe -Wall -I/usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/libpam/include -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libpam/modules/pam_deny/../../../../contrib/libpam/modules/pam_deny/pam_deny.c -o pam_deny.So >> building standard pam_deny library >> ranlib libpam_deny.a >> building shared library pam_deny.so >> ===> libpam/modules/pam_kerberosIV >> make: don't know how to make /usr/obj/usr/src/i386/usr/lib/libcrypto.a. Stop >> *** Error code 2 > Are you building with NO_OPENSSL? I just ran into this exact problem > myself overnight with my buildworld with NO_OPENSSL enabled. that's the cause. > Try this patch: thanks. will do. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message