From owner-freebsd-current  Sat Apr  6 18:51:17 2002
Delivered-To: freebsd-current@freebsd.org
Received: from w250.z064001178.sjc-ca.dsl.cnc.net (w250.z064001178.sjc-ca.dsl.cnc.net [64.1.178.250])
	by hub.freebsd.org (Postfix) with SMTP id E958537B404
	for <current@FreeBSD.ORG>; Sat,  6 Apr 2002 18:51:14 -0800 (PST)
Received: (qmail 50643 invoked by uid 1000); 7 Apr 2002 02:51:36 -0000
Date: Sat, 6 Apr 2002 18:51:14 -0800
From: Jos Backus <jos@catnook.com>
To: current@FreeBSD.ORG
Subject: Initiate de-orbit burn for <malloc.h>?
Message-ID: <20020407025136.GD41627@lizzy.catnook.com>
Reply-To: Jos Backus <jos@catnook.com>
Mail-Followup-To: current@FreeBSD.ORG
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

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?

Thoughts?

-- 
Jos Backus                 _/  _/_/_/        Santa Clara, CA
                          _/  _/   _/
                         _/  _/_/_/             
                    _/  _/  _/    _/
jos@catnook.com     _/_/   _/_/_/            use Std::Disclaimer;

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message