Date: Wed, 13 Apr 2005 08:41:20 -0600 From: Scott Long <scottl@samsco.org> To: Giorgos Keramidas <keramida@freebsd.org> Cc: David Xu <davidxu@freebsd.org> Subject: Re: HEADS-UP: Planning on deprecating libc_r for 6.0 Message-ID: <425D2F90.4020207@samsco.org> In-Reply-To: <20050413144159.GA40749@orion.daedalusnetworks.priv> References: <425D2041.7020501@samsco.org> <20050413144159.GA40749@orion.daedalusnetworks.priv>
next in thread | previous in thread | raw e-mail | index | archive | help
Giorgos Keramidas wrote: > 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? > Are there any sorts of pre-defined ELF sections that we could put deprecation info into and have the linker print it out? That way controls could be commonized for future use. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?425D2F90.4020207>