From owner-freebsd-arch@FreeBSD.ORG Wed Apr 13 14:42:08 2005 Return-Path: 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 462D016A4CE; Wed, 13 Apr 2005 14:42:08 +0000 (GMT) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0887A43D45; Wed, 13 Apr 2005 14:42:05 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])j3DEf1PA029947; Wed, 13 Apr 2005 17:41:03 +0300 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) j3DEg0Lt040902; Wed, 13 Apr 2005 17:42:00 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost)j3DEg09J040901; Wed, 13 Apr 2005 17:42:00 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Wed, 13 Apr 2005 17:42:00 +0300 From: Giorgos Keramidas To: Scott Long Message-ID: <20050413144159.GA40749@orion.daedalusnetworks.priv> References: <425D2041.7020501@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <425D2041.7020501@samsco.org> cc: arch@freebsd.org cc: re@freebsd.org cc: David Xu 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2005 14:42:08 -0000 On 2005-04-13 07:36, Scott Long 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?