Date: Tue, 30 Oct 2001 16:11:05 +0200 From: Peter Pentchev <roam@ringlet.net> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/include malloc.h Message-ID: <20011030161105.A93996@straylight.oblivion.bg> In-Reply-To: <200110250239.f9P2dfn50520@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Wed, Oct 24, 2001 at 10:39:41PM -0400 References: <200110250235.f9P2ZTU86318@freefall.freebsd.org> <200110250239.f9P2dfn50520@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 24, 2001 at 10:39:41PM -0400, Garrett Wollman wrote: > <<On Wed, 24 Oct 2001 19:35:29 -0700 (PDT), Garrett Wollman <wollman@FreeBSD.org> said: > > > Resume deorbit burn sequence for <malloc.h>. Inspection of my make logs > > reveals no programs in the standard build which hit the previous warning > > message. This change will NOT be merged to 4-stable. > > This was discussed in one of the mailing-lists a few months ago. The > postponement of 5.0 means that port maintainers have almost a year to > fix programs which still use this 10-years-obsolete header. > <malloc.h> was never part of Standard C and is was included in SUSv2. > > As the error message suggests, the correct fix for any program which > unconditionally includes <malloc.h> is to include <stdlib.h> instead. Just BTW, what is the correct test to use for malloc.h vs stdlib.h? Will __STDC__ be enough? G'luck, Peter -- If this sentence didn't exist, somebody would have invented it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011030161105.A93996>