On Sat, Apr 06, 2002 at 06:51:14PM -0800, Jos Backus wrote:
> One problem with ports is that configure will cause <malloc.h> to be used if
> it exists in /usr/include (net/rsync being the latest example), causing an
> annoying warning. So why not remove /usr/include/malloc.h, and patch those
> ports/programs that still use it to use <stdlib.h> instead?

In my opinion this situation only happens on -STABLE right now, since a
properly written configure script not just test for the header's
existence, but also tries to use it in a small example program. On
-STABLE this works (with a warning as you say) but on -CURRENT no
longer. So, configure scripts should detect that condition and act
accordingly. (And most that I have seen do) With that said, ports are
already being patched for this problem (because some hard-code the use
of malloc.h) so this should be less of a problem by the time 5.0 hits
the streets.


Szilveszter ADAM
Szombathely Hungary

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to