Request for recompilation: quantlib-python
buildd.debian.org shows that the m68k build of quantlib-python dies at
python2.1 setup.py build
QuantLib/quantlib_wrap.cpp: In function `struct PyObject * _wrap_BoundaryCondition_type(PyObject *, PyObject *, PyObject *)':
QuantLib/quantlib_wrap.cpp:2482: warning: `struct PyObject * resultobj' might be used uninitialized in this function
QuantLib/quantlib_wrap.cpp: In function `struct PyObject * _wrap_Period_units(PyObject *, PyObject *, PyObject *)':
QuantLib/quantlib_wrap.cpp:4099: warning: `struct PyObject * resultobj' might be used uninitialized in this function
QuantLib/quantlib_wrap.cpp: In function `struct PyObject * _wrap_Date_weekday(PyObject *, PyObject *, PyObject *)':
QuantLib/quantlib_wrap.cpp:4325: warning: `struct PyObject * resultobj' might be used uninitialized in this function
QuantLib/quantlib_wrap.cpp: In function `struct PyObject * _wrap_Date_month(PyObject *, PyObject *, PyObject *)':
QuantLib/quantlib_wrap.cpp:4475: warning: `struct PyObject * resultobj' might be used uninitialized in this function
make: *** wait: No child processes. Stop.
make: *** Waiting for unfinished jobs....
make: *** wait: No child processes. Stop.
Build killed with signal 15 after 170 minutes of inactivity
That might be spurious. This packages uses SWIG wrappers to the C++ library
libquantlib0. The resulting .so file is rather large:
edd@homebud:~> ls -hlS /usr/lib/python2.1/site-packages/QuantLib/
total 2.9M
-rw-r--r-- 1 root root 2.4M Nov 30 00:24 QuantLibc.so
-rw-r--r-- 1 root root 223k Nov 29 23:59 QuantLib.pyc
-rw-r--r-- 1 root root 108k Nov 29 23:35 QuantLib.py
-rw-r--r-- 1 root root 21k Nov 29 23:59 defaults.pyc
-rw-r--r-- 1 root root 14k Nov 7 06:49 defaults.py
-rw-r--r-- 1 root root 3.2k Nov 29 23:59 __init__.pyc
-rw-r--r-- 1 root root 3.1k Oct 4 07:16 __init__.py
and the compilation step for this 2.9mb baby takes a fairly long time on my
i386 (k6-II 300, 256mb ram). A small machine with little ram might cough on
it.
Could someone do me a favour and try to do this by hand (ie call
"debian/rules build") and see what happens?
Many thanks, Dirk
--
Better to have an approximate answer to the right question than a precise
answer to the wrong question. -- John Tukey as quoted by John Chambers
Reply to: