You are not logged in.

#1 2011-03-25 09:45:21

dragonfi
Member
Registered: 2010-06-11
Posts: 12

python3-scipy shared library problem in PKGBUILD

Hi,

I've tried to make a working python3-scipy package using the newest release of scipy (9.0.0). I maanged to make it work, but in a pretty hackish way.

scipy builds fine with python2, but with python3, it does not find the 'blas' and 'lapack' dependencies. I tracked down the problem to numpy.distutils.sysconfig.get_config_vars('SO').

This is the difference in the two versions:
Python2 code:

>>> from numpy import distutils
>>> from distutils import sysconfig
>>> sysconfig.get_config_vars('SO')
['.so']

Python3 code:

>>> from numpy import distutils
>>> from distutils import sysconfig
>>> sysconfig.get_config_vars('SO')
['.cpython-32mu.so']

I created the following symlinks in /usr/lib:
libblas.cpython-32mu.so --> libblas.so
liblapack.cpython-32mu.so --> liblapack.so

With theese modification, it compiles and installs fine.

I have two questions:
Why does python3-numpy uses .cpython-32mu.so for shared files instead of .so ?
How to make a clean solution in the PKGBUILD ?

Last edited by dragonfi (2011-03-25 09:46:40)

Offline

#2 2011-03-30 09:10:45

dragonfi
Member
Registered: 2010-06-11
Posts: 12

Re: python3-scipy shared library problem in PKGBUILD

Solved, maybe not the cleanest way, but it works.
I've created 2 symlink in ${srcdir} to the relevant libraries, apparently it only needed those instances on build, and can find the real libraries on it's own, after install.

PS: How do I mark this as solved? does the forum tracks it, or should I just perpend [SOLVED] in front of the first post's title?

Last edited by dragonfi (2011-03-30 09:12:59)

Offline

Board footer

Powered by FluxBB