From owner-freebsd-current Sun Apr 7 0:48:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx2.datanet.hu (mx2.datanet.hu [194.149.13.163]) by hub.freebsd.org (Postfix) with ESMTP id 76B4137B405 for ; Sun, 7 Apr 2002 00:48:48 -0800 (PST) Received: from fonix.adamsfamily.xx (nilus-235.adsl.datanet.hu [195.56.48.235]) by mx2.datanet.hu (DataNet) with ESMTP id A8D645B93 for ; Sun, 7 Apr 2002 10:48:42 +0200 (CEST) Received: from fonix.adamsfamily.xx (localhost [127.0.0.1]) by fonix.adamsfamily.xx (8.12.2/8.12.2) with ESMTP id g378mqS9000720 for ; Sun, 7 Apr 2002 10:48:52 +0200 (CEST) (envelope-from sziszi@bsd.hu) Received: (from cc@localhost) by fonix.adamsfamily.xx (8.12.2/8.12.2/Submit) id g378mpUu000719 for current@FreeBSD.ORG; Sun, 7 Apr 2002 10:48:52 +0200 (CEST) X-Authentication-Warning: fonix.adamsfamily.xx: cc set sender to sziszi@bsd.hu using -f Date: Sun, 7 Apr 2002 10:48:49 +0200 From: Szilveszter Adam To: current@FreeBSD.ORG Subject: Re: Initiate de-orbit burn for ? Message-ID: <20020407084848.GA539@fonix.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , current@FreeBSD.ORG References: <20020407025136.GD41627@lizzy.catnook.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020407025136.GD41627@lizzy.catnook.com> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, On Sat, Apr 06, 2002 at 06:51:14PM -0800, Jos Backus wrote: > One problem with ports is that configure will cause 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 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