`Hiding' libc symbols

Andrey A. Chernov ache at nagual.pp.ru
Mon May 5 16:18:48 PDT 2003


On Mon, May 05, 2003 at 18:11:35 -0500, Jacques A. Vidrine wrote:
> applications that (IMHO most legitimately, some not) define symbols
> that are technically in some standard's space, such as `snprintf',
> `strlcpy', `accept', `close', ... ?  ``Fix'' them all?  Throw them
> away?

Fix them all. It is as easy as putting
#define printf myprintf
somewhere into headers or even into CC flags. When this task is spreaded 
among corresponding ports maintainers, the number for each of them will be 
not too big.

> What about applications that are already compiled?

Leave them as is. I mean linker time error, not runtime.

> I think such fascism would result in us behaving in a very un-UNIX
> fashion.

And I think just opposite.


More information about the freebsd-arch mailing list