From owner-freebsd-arch@FreeBSD.ORG  Wed Apr 13 14:45:12 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 E6E2016A4CF; Wed, 13 Apr 2005 14:45:12 +0000 (GMT)
Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id D500443D55; Wed, 13 Apr 2005 14:45:11 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.3/8.13.1) with ESMTP id j3DEj7VS019269;
	Wed, 13 Apr 2005 16:45:07 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Giorgos Keramidas <keramida@freebsd.org>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Wed, 13 Apr 2005 17:42:00 +0300."
             <20050413144159.GA40749@orion.daedalusnetworks.priv> 
Date: Wed, 13 Apr 2005 16:45:07 +0200
Message-ID: <19268.1113403507@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: arch@freebsd.org
cc: re@freebsd.org
cc: David Xu <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:45:13 -0000

In message <20050413144159.GA40749@orion.daedalusnetworks.priv>, Giorgos Keramidas writes:
>On 2005-04-13 07:36, Scott Long <scottl@samsco.org> wrote:
>> All,
>>
>> Now that we've had working KSE for 2 years, I'm planning to declare that
>> libc_r will be deprecated in 6.0 [...]
>>
>> 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?
>
>How about modifying the dynamic linker to print a warning to stderr,
>much like mktemp(3), but let the user disable it by setting an
>environment variable, like LD_WARN_LIBC_R_DISABLE or similar?

The user can disable it by adding a line in libmap.conf so let us
not invent more handles to tweak but point the user at the right
one.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.