From owner-freebsd-arch@FreeBSD.ORG  Wed Apr 13 14:57:46 2005
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5734816A4CE; Wed, 13 Apr 2005 14:57:46 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E064D43D60; Wed, 13 Apr 2005 14:57:45 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.13.3/8.13.1) with ESMTP id j3DEueu0055383;
	Wed, 13 Apr 2005 08:56:40 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Wed, 13 Apr 2005 08:56:52 -0600 (MDT)
Message-Id: <20050413.085652.56562781.imp@bsdimp.com>
To: scottl@samsco.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <425D2041.7020501@samsco.org>
References: <425D2041.7020501@samsco.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: arch@freebsd.org
cc: re@freebsd.org
cc: davidxu@freebsd.org
Subject: Re: HEADS-UP: Planning on deprecating libc_r for 6.0
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2005 14:57:46 -0000

In message: <425D2041.7020501@samsco.org>
            Scott Long <scottl@samsco.org> writes:
: One question that has come up is how to warn the user at runtime about
: this deprecation.  Should the dynamic linker print a message to stderr
: when it gets a request to load libc_r?  Should it go to the console
: and/or syslog instead?  Should there be a way to disable these messages
: so as not to break wrapper programs that might be confused by the
: output?  Should we even bother at all with runtime warnings?

I'd do a build-time warning only.

This would allow poeple to deploy systems with libc_r and not have
annoying warnings at a customer's site.  They will know that things
are deprecated.  Also, compat librarires will be around for a while,
so doing things at runtime seems annoying...

As far as my company's use of libc_r, we don't yet know how well
non-libc_r works yet since we've not done any large threaded FreeBSD 5
applications yet.  So I can't comment on how wise/foolish this option
is with any direct experience.

Warner