Date: Wed, 12 Dec 2001 14:10:48 -0500 (EST) From: Alan E <alane@geeksrus.net> To: FreeBSD-gnats-submit@freebsd.org Subject: misc/32760: Please MFC /usr/include/malloc.h to -STABLE. Message-ID: <200112121910.fBCJAmB00653@wwweasel.geeksrus.net>
next in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112121910.fBCJAmB00653>