[Patch] Document __secure_getenv

Andreas Schwab schwab@linux-m68k.org
Fri Jul 13 09:53:00 GMT 2012


Florian Weimer <fweimer@redhat.com> writes:

> I don't want to use secure_getenv for the public symbol because I think I
> need three symbols: __secure_getenv (public, but without a default
> version) for backwards compatibility, getenv_secure (public) for the new
> interface, and __getenv_secure (GLIBC_PRIVATE) for the internal
> cross-references, both within libc itself and from libnss_hesiod and
> others.

You don't need the third name, a symbol can have more than one version.
Also, libc internal references are resolved internally via the hidden
mechanism.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



More information about the Libc-alpha mailing list