Date: Tue, 5 Mar 2002 22:59:41 +1100 From: Edwin Groothuis <edwin@mavetju.org> To: freebsd-ports@FreeBSD.ORG Subject: Re: ports/35519: kdepim port doesn't know that malloc.h is now broken Message-ID: <20020305225941.A511@k7.mavetju.org> In-Reply-To: <20020305112726.GC16804@nevermind.kiev.ua>; from never@nevermind.kiev.ua on Tue, Mar 05, 2002 at 01:27:26PM %2B0200 References: <200203042150.g24Lo2t96830@freefall.freebsd.org> <20020304230615.A43099@graf.pompo.net> <20020305112726.GC16804@nevermind.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 05, 2002 at 01:27:26PM +0200, Nevermind wrote:
> Hello, Thierry Thomas!
>
> On Mon, Mar 04, 2002 at 11:06:15PM +0100, you wrote:
>
> > > Great, thanks muchly. I'll try installing again later tonight. Someone
> > > needs to teach people to stop including malloc.h.
> >
> > What about something like:
> >
> > find ${WRKSRC} -type f | xargs ${PERL} -pi -e \
> > "s@#include.*<malloc.h>@#include <stdlib.h>@"
> >
> > in bsd.port.mk?
> I suppose it is good idea, but we should make this option on by default
> but with ability to off it.
Honestly, if software needs malloc() then the software should include
the right files. Patching it is not a good solution, patching it
by default because people are not doing it right is plain wrong.
Just my opinion.
What I was actually more wondering about was who decides that such
a file is suddenly depricated? Was that the FreeBSD community? Or
the makers of gcc? Posix complience? who? Who? WHO?
Edwin, just wondering :-)
--
Edwin Groothuis | Personal website: http://www.MavEtJu.org
edwin@mavetju.org | Interested in MUDs? Visit Fatal Dimensions:
------------------+ http://www.FatalDimensions.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020305225941.A511>