On Tue, 13 Apr 2010, Soeren Sonnenburg wrote:
> On Tue, 2010-04-13 at 11:04 -0400, Yaroslav Halchenko wrote:
> > > Any ideas how to fix it? It seems numpy is no better...
> OK I see, I just did not have this package installed. Now I stil don't
> know how to create the _d.so's for numpy and I am afraid having multiple
> packages shogun-dbg, shogun-python-dbg would be misleading. So a
myself -- I don't care -- they all could reside in the same package if
you find it easier to do so ;) unless some machinery could have helped
to automate it (unfortunately cdbs is not yet there)
> shogun-dbg should contain the _d files for python...
> If you have time to figure out how this could work - I am all yours :D
sorry that I wasn't clear:
> > ... the idea is to
> > use python*-dbg to build those libraries for -dbg package:
which is what I was pointing to, but I've forgotten that in shogun you
don't rely on distutils to build the extensions.... if you did then it
would be as simple as to use
python2.5-dbg setup.py build_ext
instead of
python2.5 setup.py build_ext
in your case, I think it should boil down just to
1. disabling optimization in *FLAGS given to gcc
2. using /usr/include/python2.5_d instead of /usr/include/python2.5
as the path for include files
3. -o into _d.so files at the end and install to the corresponding paths
may be there is smth more to do, but I've not spotted any additional
actions... could you give this a try?
--
.-.
=------------------------------ /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
