HEADS-UP: Planning on deprecating libc_r for 6.0
scottl at samsco.org
Wed Apr 13 09:49:38 PDT 2005
M. Warner Losh wrote:
> In message: <425D2041.7020501 at samsco.org>
> Scott Long <scottl at 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.
Yes, outfits like yours and Julian's are exactly what I had in mind when
I said that it would be several years before it goes away, and even then
it would live on in /usr/lib/compat.
More information about the freebsd-arch