Date: Fri, 08 Nov 2002 14:31:23 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: sgk@troutmask.apl.washington.edu Cc: akm@theinternet.com.au, eischen@pcnet1.pcnet.com, ataraxia@cox.net, current@FreeBSD.ORG Subject: Re: [PATCH] note the __sF change in src/UPDATING Message-ID: <20021108.143123.15266428.imp@bsdimp.com> In-Reply-To: <20021108184215.GA71377@troutmask.apl.washington.edu> References: <20021108174915.GA71225@troutmask.apl.washington.edu> <20021108181611.GA90784@zeus.theinternet.com.au> <20021108184215.GA71377@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20021108184215.GA71377@troutmask.apl.washington.edu>
Steve Kargl <sgk@troutmask.apl.washington.edu> writes:
: Here's the fun part. The following 5.0 libraries have the same
: version number as their 4.x counterparts. Try running a 4.x
: app linked against one of these libaries on a 5.0 machine. You
: should also note that this list may not be complete list of
: libraries suffering this problem.
:
: libalias.so.4 libbz2.so.1 libcam.so.2 libcom_err.so.2
: libcrypto.so.2 libdes.so.3 libdialog.so.4 libfetch.so.3
: libftpio.so.5 libg2c.so.1 libhistory.so.4 libipsec.so.1
: libisc.so.1 libkvm.so.2 libm.so.2 libncp.so.1
: libncurses.so.5 libopie.so.2 libpcap.so.2 libreadline.so.4
: libsmb.so.1 libssh.so.2 libutil.so.3
You've also not listed all the package binaries that have similar
problems.
Warner
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021108.143123.15266428.imp>