From owner-freebsd-bugs  Wed Dec 12 11:30:12 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP id E2E1137B416
	for <freebsd-bugs@hub.freebsd.org>; Wed, 12 Dec 2001 11:30:01 -0800 (PST)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id fBCJU1e56942;
	Wed, 12 Dec 2001 11:30:01 -0800 (PST)
	(envelope-from gnats)
Date: Wed, 12 Dec 2001 11:30:01 -0800 (PST)
Message-Id: <200112121930.fBCJU1e56942@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Robert Watson <rwatson@freebsd.org>
Subject: Re: misc/32760: Please MFC /usr/include/malloc.h to -STABLE.
Reply-To: Robert Watson <rwatson@freebsd.org>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.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-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR misc/32760; it has been noted by GNATS.

From: Robert Watson <rwatson@freebsd.org>
To: Alan E <alane@geeksrus.net>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: misc/32760: Please MFC /usr/include/malloc.h to -STABLE.
Date: Wed, 12 Dec 2001 14:27:21 -0500 (EST)

 While I'm not opposed to such a change in general, I think doing this
 before 4.5-RELEASE would be very bad idea, as it would dramatically
 increase the "make ports work" work-load before the release.  Doing this
 after 4.5-RELEASE sounds like a reasonable idea. 
 
 Robert N M Watson             FreeBSD Core Team, TrustedBSD Project
 robert@fledge.watson.org      NAI Labs, Safeport Network Services
 
 On Wed, 12 Dec 2001, Alan E wrote:
 
 > 
 > >Number:         32760
 > >Category:       misc
 > >Synopsis:       Please MFC /usr/include/malloc.h to -STABLE.
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          change-request
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Wed Dec 12 11:20:01 PST 2001
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Alan E
 > >Release:        FreeBSD 4.4-STABLE i386
 > >Organization:
 > Geeksrus.NET
 > >Environment:
 > System: FreeBSD wwweasel.geeksrus.net 4.4-STABLE FreeBSD 4.4-STABLE #0: Sun Dec 2 19:14:12 EST 2001 root@wwweasel.geeksrus.net:/usr/obj/usr/src/sys/WWWEASEL i386
 > >Description:
 > 
 > /usr/include/malloc.h on CURRENT generates an error using #error.
 > /usr/include/malloc.h on STABLE only generates a #warning.
 > 
 > This means that things (like KDE) will build in STABLE and then people try
 > to build the released ports on CURRENT and get bit by this.
 > 
 > If malloc.h were MFC'd, then we'd catch all of this stuff up front, rather
 > than after releasing new ports to the world.
 > 
 > >How-To-Repeat:
 > 
 > Compile something that does "#include <malloc.h>".
 > 
 > >Fix:
 > 
 > MFC malloc.h.
 > 
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 > 
 > To Unsubscribe: send mail to majordomo@FreeBSD.org
 > with "unsubscribe freebsd-bugs" in the body of the message
 > 
 

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