Hi again,

this thing is somewhat mysterious.

On 07:27 Tue 30 Oct 2012, Francois Bissey wrote:
> > x86_64-pc-linux-gnu-gcc: numpy/core/blasdot/_dotblas.c
> > /usr/bin/gfortran -Wall -Wl,-O1 -Wl,--as-needed -Wl,--hash-style=gnu 
> > -shared build-3.2/temp.linux-x86_64-3.2/numpy/core/blasdot/_dotblas.o 
> > -L/usr/lib64 -L/usr/lib64 -Lbuild-3.2/temp.linux-x86_64-3.2 -lblas 
> > -lpython3.2 -lgfortran -o 
> > build-3.2/lib.linux-x86_64-3.2/numpy/core/_dotblas.cpython-32.so
> > /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.4/../../../../x86_64-pc-linux-gnu/bin/ld:
> >  cannot find -lblas
> > collect2: ld returned 1 exit status


What happens here is that some setup.py calls gfortran with -lblas
instead of what is in site.cfg.  I tried various grep's across the
source tree, but I don't understand how this happens :(

Any ideas?



> It is already supposed to use pkg-config. My numpy 1.5.1 is linked
> against openblas with python-2.7.3. However I don't appear to have
> dotblas at all in numpy with python 3.2 so there may be an issue
> when compiling against python 3.2 - I will have to check my build logs.
> 
> Did it compile against python 2.7 normally?
> 
> Francois
> 
> 

-- 
Thomas Kahle
http://dev.gentoo.org/~tomka/

Attachment: signature.asc
Description: Digital signature

Reply via email to