From owner-freebsd-current@FreeBSD.ORG Sat Apr 19 15:52:37 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FC5237B401 for ; Sat, 19 Apr 2003 15:52:37 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id B1EDB43FA3 for ; Sat, 19 Apr 2003 15:52:36 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 65001 invoked from network); 19 Apr 2003 22:52:34 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 19 Apr 2003 22:52:34 -0000 X-pair-Authenticated: 209.68.2.70 Date: Sat, 19 Apr 2003 05:48:37 -0500 (CDT) From: Mike Silbersack To: freebsd-current@freebsd.org Message-ID: <20030419054430.X461@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: kernel / libc_r (KDE) breakage - UPDATING note? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Apr 2003 22:52:37 -0000 Has anyone else experienced problems with kernels from today's -CURRENT causing problems with libc_r from last week? I just cvsup'd, and the new kernels I build all cause KDE to hang in interesting ways before it can complete its startup. Jumping back to a kernel from last week makes this problem disappear. Is there an entry in UPDATING telling me to update libc_r that I missed, or is libc_r just plain broken? Thanks, Mike "I might have gotten something done in the hour I spent screwing around with this, but now I'm just frustrated and going to go watch TV" Silbersack