Date: Mon, 14 Feb 2000 21:15:57 -0800 (PST) From: Bill Trost <trost@grey.cloud.rain.com> To: FreeBSD-gnats-submit@freebsd.org Subject: i386/16722: problem with libcrypt compatibility with 3.x libraries? Message-ID: <200002150515.VAA07816@grey.cloud.rain.com>
next in thread | raw e-mail | index | archive | help
>Number: 16722
>Category: i386
>Synopsis: squid (a 3.x binary) won't run under 4.0-prerelease
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Feb 14 21:20:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator: Bill Trost
>Release: FreeBSD 4.0-20000208-CURRENT i386
>Organization:
Trost Computing
>Environment:
This is the squid22 port I was using, and it was built on or
before Nov 7, 1999. Offhand, I have no way of knowing what
version of FreeBSD it was built against, but I would assume some
-STABLE snapshot of 3.3 or 3.4.
>Description:
When I run "squid -N -X" against my newly installed OS, I
eventually get the following error:
/usr/libexec/ld-elf.so.1: /usr/local/sbin/squid: Undefined symbol "MD5Init"
"ldd squid" says the following:
libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x280be000)
libm.so.2 => /usr/lib/libm.so.2 (0x280c0000)
libc.so.3 => /usr/lib/libc.so.3 (0x280db000)
>How-To-Repeat:
With the details as clumsy as they are (sorry), I would suggest
grabbing a squid package for 3.x, installing it under 4.0, and
seeing what happens.
I will hang onto a tarball of my 3.x version of squid should it
come in handy.
>Fix:
I assume that compat3x needs a libcrypt, which probably means that
libcrypt's version number needs upgrading. Have fun...
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002150515.VAA07816>