I found an even simpler solution: use the -mstackrealign GCC option to
build the shared library.
--
Olivier
--
http://mail.python.org/mailman/listinfo/python-list
Replying to myself:
haypo found the origin of the problem. Apparently this problem stems
from a GCC bug [1] (that should be fixed on x86 as of version 4.4).
The bug is that GCC does not always ensure the stack to be 16 bytes
aligned hence the "__m128 myvector" local variable in the previous
code
2008/11/25 <[EMAIL PROTECTED]>:
> On Nov 25, 4:34 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
>>
>> You can't use ctypes for C++, only for C-style APIs.
>>
>> Diez
>
> With some work, you can convert your C++ objects to PyObject* and then
> return the latter in a function with C bindings.
h
Hello,
It seems that I am able to reproduce the same problem as reported
earlier on this list by someone else:
http://mail.python.org/pipermail/python-list/2008-October/511794.html
Similar setup: python 2.5.2 / gcc (Ubuntu 4.3.2-1ubuntu11) from
Intrepid on 32bit intel Core 2 Duo. I can confir
gene tani a écrit :
> Shahriar Shamil Uulu wrote:
>> Thank you, for your directions and advices.
>> shahriar ...
>
> also look:
>
> http://spyced.blogspot.com/2005/09/how-well-do-you-know-python-part-9.html
>
> whihc mentions twisted.python.reflect.findInstances(sys.modules, str)
> and objgrep,
Wolfgang Grafen a écrit :
> What happened to the Vaults of Parnassus? It was always my
> favourite resource for Python code since ever. The latest
> entry is now 8/23. It has been up to date for years but now...
> What a pity!
Everybody is using the cheeseshop now:
http://cheeseshop.python.org/py
