Re: [Bug-XBoard] configure doesn't do the right thing after no malloc.h detected on MacOSX

[Tim Mann]

I don't remember anything about the #include <malloc.h>. It might have
been added for some ancient Unix that didn't have stdlib.h yet, or
might have been a mistake from the start.

On Sun, Apr 3, 2011 at 8:28 PM, Arun Persaud <address@hidden> wrote:
> Hi
>
> On 04/03/2011 06:55 AM, Dima Pasechnik wrote:
>> There is no malloc.h header on MacOSX 10.6,
>> which is of course not a problem, but engineoutput.c still includes malloc.h
>> and does not compile because of this.
>> Presenting it with a dummy (empty, say) malloc.h) allows
>> the program to compile, build, and work just fine, so this is just a 
>> question of
>> making configure do the right thing in this case.
>
> thanks for reporting, should be fixed now in the latest git version.
>
> I added a #if HAVE_MALLOC_H...#endif around it.
>
> I start to think that we don't need to include malloc.h at all though,
> since malloc is defined in stdlib and malloc.h adds other protodyptes.
> Seems as if you can compile it without malloc.h anyway... we'll look
> into it. I CC'ed Tim and HGM on it, they probably know more about this...
>
> Arun
>