From owner-freebsd-stable Tue Sep 18 0:56:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 5742A37B416; Tue, 18 Sep 2001 00:56:16 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f8I7uEv22456; Tue, 18 Sep 2001 09:56:14 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: stable@freebsd.org, re@freebsd.org Subject: 4.4-RELEASE libcrypto.so.[12] confusion/problem... From: Poul-Henning Kamp Date: Tue, 18 Sep 2001 09:56:14 +0200 Message-ID: <22454.1000799774@critter> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Imagine this: install 4.4-RELEASE install 3rd party software compiled on 4.x observe the lack of libcrypto.so.1 Now, the fix, as it transpires, is to install the "compat4x" distribution, but I'd be damned if that sounds even remotely logical to me and it is certainly not the first thing I would even think about as a "normal user" [tm]. Also, I'm not sure that installing compat4x on a 4.4 system wouldn't get me an indesirable libc anyway... I think that libcrypto.so.1 (and any other down-rev'ed libraries) from the -stable branch should be automatically installed on 4.x... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message