From owner-freebsd-current Sat Feb 17 16:38:38 2001 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 29D4737B684 for ; Sat, 17 Feb 2001 16:38:32 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.2/8.11.2) with ESMTP id f1I0cMj00486; Sat, 17 Feb 2001 16:38:26 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20010217162314.00a69850@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Sat, 17 Feb 2001 16:38:22 -0800 To: The Hermit Hacker From: Manfred Antar Subject: Re: got stuck in the current __sF foo... Cc: , In-Reply-To: References: <5.0.2.1.2.20010217154335.00a696e0@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:17 PM 2/17/2001 -0400, The Hermit Hacker wrote: >I just got hurt by this, in a sense ... buildworld and installworld all >worked great, but as soon as I tried to a 'startx', it told me that >libm.so.2 had an unresolved symbol __sF ... I just rebuilt my X, figure >just the result of the bump in libm.so.n major ... > > I don't think any of the libs were bumped recently except for libc and that was backed out. There was a patch posted that bumped some of the libs but that was withdrawn. I think you might have libs built from some of the stuff that was backed or not a totally current source. I'm using X compiled on the 8th of Feb with a current world as of 2 hours ago and no problem Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message