oki doki ;)
so, after all was taken care of to build rpy without optimization and
stripping, gdb showed:
1846 #ifdef WITH_NUMERIC
1847 if(use_numeric)
1848 init_numeric();
1849 #endif
1850
1851 if(first==1)
(gdb) n
1848 init_numeric();
(gdb) s
init_numeric () at src/rpymodule2092.c:1823
1823 if(use_numeric)
(gdb) s
1825 import_array();
(gdb) s
_import_array () at
/usr/lib/python2.5/site-packages/numpy/core/include/numpy/__multiarray_api.h:971
and 'eureka' -- I've forgotten about tiny elephant: numpy... I had 1:1.2.1-1.1
whenever sid has 1:1.3.0-3 ... I've installed 1.3.0-3 and now it seems to
import rpy just fine. So, I guess, python-rpy should require numpy >= 1.3.0 ?
could you verify that you have similar case? ;)
> Matthias: All of a sudden the 'rpy' R module for Python segfauls on Debian
> (see original bug report #544564) whereas the courtesy backport we do via the
> R "CRAN" network works on my Ubuntu Jaunty amd64 works. Did something
> change at Debian's Python end?
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
