[PythonLabs] Re: [Zope-Coders] Signal handling

[Jens Vagelpohl]

thanks for the help. commenting out the line that includes malloc.h allows 
the compilation to finish.

now i'm faced with other problems trying to use the standard start script,
  i don't remember having any of those ever before:

[statler:/tmp/Zope] jens% ./start -D
Traceback (most recent call last):
   File "/tmp/Zope/z2.py", line 582, in ?
     zdaemon.run(sys.argv, os.path.join(CLIENT_HOME, Zpid),
NameError: name 'CLIENT_HOME' is not defined

interestingly, this seems to be the first time in the whole module that 
CLIENT_HOME is referenced anywhere.

argh!!!!!  i'm not going to pursue this any further tonight.

jens



On Wednesday, June 12, 2002, at 12:10 , Tim Peters wrote:

> [Jens Vagelpohl]
>> yes there is::
>>
>> [statler:~] jens% locate malloc.h
>> /usr/include/objc/malloc.h
>> /usr/include/sys/malloc.h
>
> 1. Are either of those on the standard include path for your compiler?
>    Since it can't find it, I bet not <wink>.
>
> 2. Can you try again after simply deleting the
>
> #include <malloc.h>
>
>    line in lib/python/BTrees/sorters.c?  A std-conforming C compiler
>    should supply the needed prototypes via the earlier #include of
>    stdlib.h.  Including malloc.h is a possibly <wink> bad habit I've
>    had since K&R C days.
>
> sorters.c is relatively new code, which is why this never popped up before.