`Hiding' libc symbols
Julian Elischer
julian at elischer.org
Tue May 6 11:02:28 PDT 2003
On Tue, 6 May 2003, Jacques A. Vidrine wrote:
> On Tue, May 06, 2003 at 10:09:19AM -0700, David O'Brien wrote:
> > On Mon, May 05, 2003 at 12:54:28PM -0500, Jacques A. Vidrine wrote:
> > > > > I'm backing out the commit in good faith and in the hopes that the
> > > > > big picture comes more clearly into focus.
> > > >
> > > > Thanks.
> > >
> > > Do you also want to `fix' the other ports that define their own strlcpy?
> >
> > Ports have maintainers. Please create a PR for them.
>
> But gee, the problem is that the ports themselves are not really
> in error, unless one is a standards fascist that believes that an
> application can never define any function that might be in some
> standard's namespace.
If you could do your census again but this time showing which symbols
clash we would have a better idea of what we are talking about..
Probably most of these packages have these function 'in case' the system
does not. You can also bet that if compiled on Linux they don't include
these functions if Linux has them, so I'm willing to bet that many of
them have ways to turn off much of the excess stuff.
>
> Cheers,
> --
> Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal
> nectar at celabo.org . jvidrine at verio.net . nectar at freebsd.org . nectar at kth.se
> _______________________________________________
> freebsd-arch at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arch
> To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"
>
More information about the freebsd-arch
mailing list