`Hiding' libc symbols

[Terry Lambert]

"Jacques A. Vidrine" wrote:
> On Tue, May 06, 2003 at 09:56:06AM +0200, Harti Brandt wrote:
> > There is no guarantee that you 'fix' the port by hiding the symbol.  You
> > may as well break it. This depends on the function itself and on the
> > internal relationships in libc. You have to go through each individual
> > port and see what happens anyway.
> 
> Please explain.  I _am_ guaranteed that keeping the port from hijacking
> strlcpy calls in libc will not break the port.  How could the port rely
> on the internals of libc?

Have you looked at the "electric fence" port lately?

-- Terry