From owner-freebsd-current Sat Feb 17 18:14: 5 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 6118637B503 for ; Sat, 17 Feb 2001 18:14:03 -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 f1I2Duj27210; Sat, 17 Feb 2001 18:13:56 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20010217180332.00a41d08@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Sat, 17 Feb 2001 18:13:56 -0800 To: Warner Losh , The Hermit Hacker From: Manfred Antar Subject: Re: got stuck in the current __sF foo... Cc: mjacob@feral.com, current@FreeBSD.ORG In-Reply-To: <200102180200.f1I20tW93107@harmony.village.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:00 PM 2/17/2001 -0700, Warner Losh wrote: >What version of src/lib/libc/stdio/findfp.c do you have? > >I'm using 1.15 here w/o any problems: >static const char rcsid[] = > "$FreeBSD: src/lib/libc/stdio/findfp.c,v 1.15 2001/02/16 21:09:49 imp Exp $"; > >Warner > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message There was a time when current ( a couple of days earlier this week) was volatile !! I had a system running for awhile with the new libc.so.5XXXXXXXX. I started recompiling all the ports and gave up as it didn't look like the new libc.so.5XXXXXXX was go to stay around and I didn't want to do this twice. I ended up newfs my hard drive and restoring from Feb 9 and then bringing the sources up to current (after the libc and stdio changes were backed out and modified) and doing a make world . Everything seems to be working fine since then. 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