From owner-freebsd-current Tue Nov 6 17: 8:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19]) by hub.freebsd.org (Postfix) with ESMTP id 4A86537B405 for ; Tue, 6 Nov 2001 17:08:22 -0800 (PST) Received: (from mike@localhost) by coffee.q9media.com (8.11.6/8.11.6) id fA71E6v36896; Tue, 6 Nov 2001 20:14:06 -0500 (EST) (envelope-from mike) Date: Tue, 6 Nov 2001 20:14:06 -0500 From: Mike Barcroft To: Jan Stocker Cc: freebsd-current@FreeBSD.ORG Subject: Re: malloc.h Message-ID: <20011106201405.D33972@coffee.q9media.com> References: <000501c16727$b3772540$fe02010a@twoflower.liebende.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000501c16727$b3772540$fe02010a@twoflower.liebende.de>; from Jan.Stocker@t-online.de on Wed, Nov 07, 2001 at 02:01:15AM +0100 Organization: The FreeBSD Project 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 Jan Stocker writes: > I completly reinstalled my system in the last days. Many ports have a > problem searching prototypes in malloc.h which have been moved to stdlib.h > (which is displayed as error in malloc.h). I think a better solution is to > replace the error-statement with a warning and do a #include in > the malloc.h file. If you dont, you have to take care of many c and h files > and patch em all (not a nice work for the porters...) > > Jan See section 19.2.1.4 in the FreeBSD Handbook. Specificly, you need to review the commit logs and prior discussion before posting messages like this. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message