Date: Fri, 22 Aug 2008 08:19:05 -0700 (PDT) From: Pedro Giffuni <pfgshield-freebsd@yahoo.com> To: ports@freebsd.org Cc: Luigi Rizzo <rizzo@iet.unipi.it> Subject: Re: best way to work around <malloc.h> vs <stdlib.h> ? Message-ID: <312062.64561.qm@web32706.mail.mud.yahoo.com>
next in thread | raw e-mail | index | archive | help
FWIW; One of the projects in COIN-OR found it unacceptable to ifdef malloc.h with= __STDC__. The reason is that other systems, especically AIX, use malloc.h = for non standard malloc-related functions, and including malloc.h had no il= l effect on other platforms. At the end they ifndef'ed it for __FreeBSD__. - dlmalloc and ptmalloc define malloc_usable_size() in malloc.h - FreeBSD defines malloc_usable_size() in malloc_np.h I am the minority here but I think we should go back to issuing a simple wa= rning and continue. The known packages are already fixed and being so picky= justs make life a little bit more difficult for newcomers. Pedro. =0A=0A__________________________________________________=0ADo You Yahoo!?= =0APoco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tan= to spazio gratuito per i tuoi file e i messaggi =0Ahttp://mail.yahoo.it
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?312062.64561.qm>