Re: HEADS-UP: Planning on deprecating libc_r for 6.0

From: Scott Long (scottl_at_samsco.org)
Date: 04/13/05

  • Next message: Poul-Henning Kamp: "Re: HEADS-UP: Planning on deprecating libc_r for 6.0" 
    Date: Wed, 13 Apr 2005 08:41:20 -0600
To: Giorgos Keramidas <keramida@freebsd.org>

    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
    _______________________________________________
    freebsd-arch@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-arch
    To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"

  • Next message: Poul-Henning Kamp: "Re: HEADS-UP: Planning on deprecating libc_r for 6.0"

    Relevant Pages