[PyKDE] SIP 0.9 on HP-UX 10.20

[Martin_Doering at mn.man.de]

Hi, Listers!

After having some "nice" experiences in trying to use and install gtk+ as a
widget-library for python I now switched to Qt (i got this installed in 10
min.).

But I do not get SIP 0.9 compiled on HP-UX. Has somebody done this job? 

I configured:

CC="cc -Ae" CFLAGS="-O" ./configure --x-includes=/usr/include/X11R6

Here all the messages I got from make:

No suffix list.
make  all-recursive
No suffix list.
Making all in sip
Making all in siplib
/bin/sh ../libtool --mode=compile CC -DHAVE_CONFIG_H -I. -I. -I.. -DSIP_QT_SUPPORT -I/usr/local/qt/include  -I/usr/include/X11R6
-I/usr/local/include/python1.5  -fno-exceptions  -c siplib.cpp
rm -f .libs/siplib.lo
CC -DHAVE_CONFIG_H -I. -I. -I.. -DSIP_QT_SUPPORT -I/usr/local/qt/include
-I/usr/include/X11R6 -I/usr/local/include/python1.5 -fno-exceptions -c  +Z -DPIC
siplib.cpp -o .libs/siplib.lo
CC: warning: unknown option: "-fno-exceptions": use +help for online
documentation. (901)
CC: "/usr/local/include/python1.5/longobject.h", line 78: warning: two long
declarators (162)
CC: "/usr/local/include/python1.5/longobject.h", line 79: warning: two long
declarators (162)
CC: "/usr/local/include/python1.5/longobject.h", line 80: warning: two long
declarators (162)
CC: "/usr/local/include/python1.5/longobject.h", line 81: warning: two long
declarators (162)
CC: "/usr/local/qt/include/qglobal.h", line 300: warning: "bool" is a future
reserved word (215)
CC: "siplib.cpp", line 652: warning: op not used (117)
CC: "siplib.cpp", line 1153: error: bad argument 1 type for Py_Free(): PyObject*
* (char * expected) (1264)
CC: "siplib.cpp", line 1226: error: bad argument 1 type for Py_Free(): PyObject*
* (char * expected) (1264)
*** Error exit code 1

Stop.
*** Error exit code 1

Stop.
*** Error exit code 1

Stop.



In siplib.cpp line 1153 is the second line of:

if (sipThis -> varObjs != NULL)
Py_Free(sipThis -> varObjs);


In /usr/local/include/python1.5/mymalloc.h I found the following:

/* Two sets of function wrappers around malloc and friends; useful if
you need to be sure that you are using the same memory allocator as
Python.  Note that the wrappers make sure that allocating 0 bytes
returns a non-NULL pointer, even if the underlying malloc doesn't.
The Python interpreter continues to use PyMem_NEW etc. */

/* These wrappers around malloc call PyErr_NoMemory() on failure */
extern DL_IMPORT(ANY *) Py_Malloc Py_PROTO((size_t));
extern DL_IMPORT(ANY *) Py_Realloc Py_PROTO((ANY *, size_t));
extern DL_IMPORT(void) Py_Free Py_PROTO((ANY *));


But my knowledge abou C/C++ is too bad. Any Ideas?


Thanks in advance,

Martin Doering