From owner-freebsd-questions Fri Jul 27 19:43:34 2001 Delivered-To: freebsd-questions@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-149.dsl.lsan03.pacbell.net [64.169.104.149]) by hub.freebsd.org (Postfix) with ESMTP id B3F0937B406 for ; Fri, 27 Jul 2001 19:43:30 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 94CCB66B25; Fri, 27 Jul 2001 19:43:29 -0700 (PDT) Date: Fri, 27 Jul 2001 19:43:29 -0700 From: Kris Kennaway To: Rob Cc: Weevil , freebsd-questions@FreeBSD.ORG Subject: Re: libc.so.5 missing in FreeBSD 4.3 -- why? Message-ID: <20010727194328.A57900@xor.obsecurity.org> References: <01072723010600.02571@apex.home> <3B620103.2743904B@home.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B620103.2743904B@home.com>; from europax@home.com on Fri, Jul 27, 2001 at 05:02:11PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 27, 2001 at 05:02:11PM -0700, Rob wrote: > Weevil wrote: > >=20 > > Hi, > >=20 > > I notice a lot of apps complaining these days about not finding libc.so= .5, > > notably the *freebsd port* of KDE! The FreeBSD 5.0-CURRENT package, yes ;-) You installed the wrong one. Kris --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7YibQWry0BWjoQKURAhsdAKCguDki9QmoNPtUpFTJvSVbO4F4wwCdGJnE +5EFeito2tnM5aeflubZcNo= =eVLY -----END PGP SIGNATURE----- --wac7ysb48OaltWcw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message