From alane@geeksrus.net  Wed Dec 12 11:11:50 2001
Return-Path: <alane@geeksrus.net>
Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82])
	by hub.freebsd.org (Postfix) with ESMTP id 82C8037B405
	for <FreeBSD-gnats-submit@freebsd.org>; Wed, 12 Dec 2001 11:11:49 -0800 (PST)
Received: (from alane@localhost)
	by wwweasel.geeksrus.net (8.11.6/8.11.6) id fBCJAmB00653;
	Wed, 12 Dec 2001 14:10:48 -0500 (EST)
	(envelope-from alane)
Message-Id: <200112121910.fBCJAmB00653@wwweasel.geeksrus.net>
Date: Wed, 12 Dec 2001 14:10:48 -0500 (EST)
From: Alan E <alane@geeksrus.net>
Reply-To: Alan E <alane@geeksrus.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Please MFC /usr/include/malloc.h to -STABLE.
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         32760
>Category:       misc
>Synopsis:       Please MFC /usr/include/malloc.h to -STABLE.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Dec 12 11:20:01 PST 2001
>Closed-Date:    Mon Jul 14 03:20:55 PDT 2003
>Last-Modified:  Mon Jul 14 03:20:55 PDT 2003
>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:

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
 > 
 

From: Sheldon Hearn <sheldonh@starjuice.net>
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 21:29:37 +0200

 On Wed, 12 Dec 2001 14:10:48 EST, Alan E wrote:
 
 > /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.
 
 The problem with merging the change onto the stable branch is that it's
 a serious change of interface in the middle of the lifetime of a major
 release (4.x).
 
 Sure, POSIX-conformant software should look for the prototype in the
 right place, but we try quite hard to keep point release upgrades as
 painless as possible.
 
 Ciao,
 Sheldon.
State-Changed-From-To: open->suspended 
State-Changed-By: schweikh 
State-Changed-When: Wed Aug 21 08:11:47 PDT 2002 
State-Changed-Why:  
As Sheldon points out, this won't be MFCd on the 4-STABLE branch 
due to the reasons stated. Once 4-STABLE is no longer maintained, 
this PR can be closed. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=32760 
State-Changed-From-To: suspended->closed 
State-Changed-By: kris 
State-Changed-When: Mon Jul 14 03:19:42 PDT 2003 
State-Changed-Why:  
malloc.h should not be deprecated in the RELENG_4 branch.  We 
already have the ports under control, so this isn't an issue. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=32760 
>Unformatted:
