[prev in list] [next in list] [prev in thread] [next in thread]
List: pykde
Subject: Re: [PyKDE] SIP 0.9 on HP-UX 10.20
From: Rob Cecil <rceci () master ! adams ! com>
Date: 1999-10-08 16:14:30
[Download RAW message or body]
Incidentally,
I will have a build of PyQt using the native aCC compiler on hpux10.20 available in \
the next few weeks - I could send you the libs if you are interested.
Rob
Martin_Doering@mn.man.de wrote:
> 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
>
> _______________________________________________
> PyKDE mailing list PyKDE@mats.gmd.de
> http://mats.gmd.de/mailman/listinfo/pykde
--
> Rob Cecil | Senior Development Engineer |
> rceci@adams.com | Product Development |
> (734) 913-9351 | Mechanical Dynamics, Inc. (www.adams.com) |
--------------------------------------------------------------------
"an interconnected mass of livers and pancreas and lungs and
little sharp pointy things and the occasional exploding
kidney." - Perl hacker/maintainer on internals of the Perl kernel.
[Attachment #3 (text/html)]
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Incidentally,
<p>I will have a build of PyQt using the native aCC compiler on hpux10.20
available in the next few weeks - I could send you the libs if you are
interested.
<p>Rob
<br>
<p>Martin_Doering@mn.man.de wrote:
<blockquote TYPE=CITE>Hi, Listers!
<p>After having some "nice" experiences in trying to use and install gtk+
as a
<br>widget-library for python I now switched to Qt (i got this installed
in 10
<br>min.).
<p>But I do not get SIP 0.9 compiled on HP-UX. Has somebody done this job?
<p>I configured:
<p>CC="cc -Ae" CFLAGS="-O" ./configure --x-includes=/usr/include/X11R6
<p>Here all the messages I got from make:
<p>No suffix list.
<br>make all-recursive
<br>No suffix list.
<br>Making all in sip
<br>Making all in siplib
<br>/bin/sh ../libtool --mode=compile CC -DHAVE_CONFIG_H -I. -I. -I.. \
-DSIP_QT_SUPPORT
-I/usr/local/qt/include -I/usr/include/X11R6
<br>-I/usr/local/include/python1.5 -fno-exceptions -c siplib.cpp
<br>rm -f .libs/siplib.lo
<br>CC -DHAVE_CONFIG_H -I. -I. -I.. -DSIP_QT_SUPPORT -I/usr/local/qt/include
<br>-I/usr/include/X11R6 -I/usr/local/include/python1.5 -fno-exceptions
-c +Z -DPIC
<br>siplib.cpp -o .libs/siplib.lo
<br>CC: warning: unknown option: "-fno-exceptions": use +help for online
<br>documentation. (901)
<br>CC: "/usr/local/include/python1.5/longobject.h", line 78: warning:
two long
<br>declarators (162)
<br>CC: "/usr/local/include/python1.5/longobject.h", line 79: warning:
two long
<br>declarators (162)
<br>CC: "/usr/local/include/python1.5/longobject.h", line 80: warning:
two long
<br>declarators (162)
<br>CC: "/usr/local/include/python1.5/longobject.h", line 81: warning:
two long
<br>declarators (162)
<br>CC: "/usr/local/qt/include/qglobal.h", line 300: warning: "bool" is
a future
<br>reserved word (215)
<br>CC: "siplib.cpp", line 652: warning: op not used (117)
<br>CC: "siplib.cpp", line 1153: error: bad argument 1 type for Py_Free():
PyObject*
<br>* (char * expected) (1264)
<br>CC: "siplib.cpp", line 1226: error: bad argument 1 type for Py_Free():
PyObject*
<br>* (char * expected) (1264)
<br>*** Error exit code 1
<p>Stop.
<br>*** Error exit code 1
<p>Stop.
<br>*** Error exit code 1
<p>Stop.
<p>In siplib.cpp line 1153 is the second line of:
<p>if (sipThis -> varObjs != NULL)
<br>Py_Free(sipThis -> varObjs);
<p>In /usr/local/include/python1.5/mymalloc.h I found the following:
<p>/* Two sets of function wrappers around malloc and friends; useful if
<br>you need to be sure that you are using the same memory allocator as
<br>Python. Note that the wrappers make sure that allocating 0 bytes
<br>returns a non-NULL pointer, even if the underlying malloc doesn't.
<br>The Python interpreter continues to use PyMem_NEW etc. */
<p>/* These wrappers around malloc call PyErr_NoMemory() on failure */
<br>extern DL_IMPORT(ANY *) Py_Malloc Py_PROTO((size_t));
<br>extern DL_IMPORT(ANY *) Py_Realloc Py_PROTO((ANY *, size_t));
<br>extern DL_IMPORT(void) Py_Free Py_PROTO((ANY *));
<p>But my knowledge abou C/C++ is too bad. Any Ideas?
<p>Thanks in advance,
<p>Martin Doering
<p>_______________________________________________
<br>PyKDE mailing list PyKDE@mats.gmd.de
<br><a href="http://mats.gmd.de/mailman/listinfo/pykde">http://mats.gmd.de/mailman/listinfo/pykde</a></blockquote>
<pre>--
> Rob Cecil | Senior \
> Development Engineer \
> |
> rceci@adams.com | Product \
> Development \
> |
> (734) 913-9351 | Mechanical Dynamics, Inc. \
> (www.adams.com) |
--------------------------------------------------------------------
"an interconnected mass of livers and pancreas and lungs and
little sharp pointy things and the occasional exploding
kidney." - Perl hacker/maintainer on internals of the Perl kernel.</pre>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic