From owner-freebsd-current@FreeBSD.ORG Sun May 11 04:21:19 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 42D4637B401 for ; Sun, 11 May 2003 04:21:19 -0700 (PDT) Received: from mail.rdslink.ro (mail.rdslink.ro [193.231.236.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 5F2FD43FE9 for ; Sun, 11 May 2003 04:21:17 -0700 (PDT) (envelope-from enache@rdslink.ro) Received: (qmail 7134 invoked from network); 11 May 2003 11:24:28 -0000 Received: from unknown (HELO ratsnest.hole) (10.100.0.30) by mail.rdslink.ro with SMTP; 11 May 2003 11:24:28 -0000 Date: Sun, 11 May 2003 14:22:47 +0300 From: Enache Adrian To: current@freebsd.org Message-ID: <20030511112247.GA794@ratsnest.hole> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i cc: deischen@freebsd.org Subject: bin/51535, bin/49087 - please do something about libc_r bugs 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: Sun, 11 May 2003 11:21:19 -0000 There are two PRs I submitted about blatant bugs in libc_r: bin/49087 bin/51535 the first is something one can live with it; the second is far more serious and already caused a lot of naughty breakage; both affect programs linked against libc_r, even if they don't use a single bit of the pthread_* stuff. The second seems to have propagated to the -STABLE branch too (or the other way around ?) and to NetBSD and OpenBSD. I guess libc_r will still be the default for a period of time - so please take a look at those bugs and do something about them before 5.1. Regards, Adi