recent 5.4-PRE regression: Could not resync/reset buffers

Kris Kennaway kris at
Sun Apr 3 12:26:22 PDT 2005

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:
> #> 
> #> > The trace doesn't look too wierd, otherwise.  There was a warning about
> #> > having and causing a potential conflict during
> #> > compile... It seems to find the correct lib, but later also opens
> #> 
> #> 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.
> 	I am in agreement with you here in general terms.  Specifically
> though, there's not much chance of getting rid of, because half
> the system uses it in some way (I just mv'd it once and things we very pear
> 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: 
> -r--r--r--  1 root  wheel   125920 Sep 21  2004
> -r--r--r--  1 root  wheel   233624 Sep 21  2004
> which haven't been touched by further upgrades (I use 'INSTALL=install'
> instead of 'INSTALL=install -C' in /etc/make.conf).  
> At this point, I haven't yet discovered how to solve this predicament. Even
> portupgrade is tied to via ruby. 

You need to rebuild every port that uses libm so that it is relinked
to 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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the freebsd-stable mailing list