Date: Sun, 3 Apr 2005 12:26:20 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Shaun Jurrens <shaun@shamz.net>, Kris Kennaway <kris@obsecurity.org>, Doug White <dwhite@gumbysoft.com>, freebsd-stable@freebsd.org Subject: Re: recent 5.4-PRE regression: Could not resync/reset buffers Message-ID: <20050403192620.GA28348@xor.obsecurity.org> In-Reply-To: <20050403095908.GH19717@atreides.freenix.no> References: <20050401204142.GE19717@atreides.freenix.no> <20050401190457.S94922@carver.gumbysoft.com> <20050402233950.GG19717@atreides.freenix.no> <20050402234453.GA2430@xor.obsecurity.org> <20050403095908.GH19717@atreides.freenix.no>
next in thread | previous in thread | raw e-mail | index | archive | help
--nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 03, 2005 at 11:59:08AM +0200, Shaun Jurrens wrote: > On Sat, Apr 02, 2005 at 03:44:53PM -0800, Kris Kennaway wrote: > #> On Sun, Apr 03, 2005 at 01:39:50AM +0200, Shaun Jurrens wrote: > #>=20 > #> > The trace doesn't look too wierd, otherwise. There was a warning ab= out > #> > having libm.so.2 and libm.so.3 causing a potential conflict during > #> > compile... It seems to find the correct lib, but later also opens li= bm.so.2 > #>=20 > #> That's a problem on your system that you should fix, then. It may not > #> be the cause of this problem, but it can definitely cause problems and > #> you need to rule it out. >=20 > I am in agreement with you here in general terms. Specifically > though, there's not much chance of getting rid of libm.so.2, because half > the system uses it in some way (I just mv'd it once and things we very pe= ar > shaped fast). This, iirc, was some problem at 5.3-R with a version bump > that broke things on amd64 at least. One noticed quickly that the binary > pkg for cvsup needed this library, iirc. my /lib directory has what > appears to be at least two such instances of stale libraries:=20 >=20 > -r--r--r-- 1 root wheel 125920 Sep 21 2004 libm.so.2 > -r--r--r-- 1 root wheel 233624 Sep 21 2004 libreadline.so.4 >=20 > which haven't been touched by further upgrades (I use 'INSTALL=3Dinstall' > instead of 'INSTALL=3Dinstall -C' in /etc/make.conf). =20 >=20 > At this point, I haven't yet discovered how to solve this predicament. Ev= en > portupgrade is tied to libm.so.2 via ruby.=20 You need to rebuild every port that uses libm so that it is relinked to libm.so.3 only. The easiest way to do this is to upgrade everything, e.g. portupgrade -fa or portupgrade -faPP if you want to use precompiled packages. Kris --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCUENcWry0BWjoQKURAg3OAJwPntOew+7PXTM3CLsZfVUiSp7wywCg+4BN nNuFKgFMAGBIp+sfYRsg6AY= =tqn3 -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050403192620.GA28348>