Date: Sun, 7 Apr 2002 10:48:49 +0200 From: Szilveszter Adam <sziszi@bsd.hu> To: current@FreeBSD.ORG Subject: Re: Initiate de-orbit burn for <malloc.h>? Message-ID: <20020407084848.GA539@fonix.adamsfamily.xx> In-Reply-To: <20020407025136.GD41627@lizzy.catnook.com> References: <20020407025136.GD41627@lizzy.catnook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, 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. -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020407084848.GA539>