[SciPy-user] Re: (long) Weave installation problems on Linux

Pearu Peterson pearu at cens.ioc.ee
Mon Dec 9 05:18:11 EST 2002


On Mon, 9 Dec 2002, Leighton Pritchard wrote:

> Is there another source for this, as I'm still getting errors of:
> 
> ==================================================
> 
> /usr/local/lib/python2.2/site-packages/weave/blitz-20001213/blitz/ops.h:220: no
>     match for `std::complex<float>& / double&' operator
> 
> ===================================================
> 
> /home/lep/.python22_compiled/211372/sc_a6df888dc732b38ae7a4c5fa1063b4251.cpp: 
> In
>     function `PyObject* compiled_func(PyObject*, PyObject*)':
> /home/lep/.python22_compiled/211372/sc_a6df888dc732b38ae7a4c5fa1063b4251.cpp:649: 
> no
>     match for `std::string& < int' operator
> /home/lep/.python22_compiled/211372/sc_a6df888dc732b38ae7a4c5fa1063b4251.cpp:653: 
> no
>     match for `std::string& + int' operator
> /usr/include/g++-v3/bits/stl_bvector.h:267: candidates are:
>     std::_Bit_const_iterator std::operator+(int, const
>     std::_Bit_const_iterator&)
> /usr/include/g++-v3/bits/stl_bvector.h:208:                 std::_Bit_iterator
>     std::operator+(int, const std::_Bit_iterator&)
> 
> =====================================================

In my case, gcc 3.1.1, the first error is the same but in the second case
I only get the following messages:

=======================
/home/users/pearu/.python22_compiled/14033/sc_a6df888dc732b38ae7a4c5fa1063b4251.cpp: In
   function `PyObject* compiled_func(PyObject*, PyObject*)':
/home/users/pearu/.python22_compiled/14033/sc_a6df888dc732b38ae7a4c5fa1063b4251.cpp:649: no
   match for `std::string& < int' operator
/home/users/pearu/.python22_compiled/14033/sc_a6df888dc732b38ae7a4c5fa1063b4251.cpp:653: no
   match for `std::string& + int' operator
=======================

though weave.test(10) summary indicates only one error:

----------------------------------------------------------------------
Ran 184 tests in 499.753s

FAILED (errors=1)
<unittest.TextTestRunner instance at 0x84833a4>
>>>

> Or is this what you meant by 'less issues'? ;)

Yes, exactly ;)

Pearu




More information about the SciPy-User mailing list