Application kig (kededu) has no python scripting support, and a lot of minor issues. In this italian post - http://forums.gentoo.org/viewtopic.php?p=2056658 - motaboy explained me it depends about package boost. kig needs boost as a dipendence, but portage doesn't know that. Emerging boost and reemerging kdeedu solves the problem. In my attachment, I've joined a lot of output about compilation. I used two independent installations, 32-bit and 64-bit, on a laptop amd64. Reproducible: Always Steps to Reproduce: 1. run kig 2. search "Objects->Other->Script Python " button 2' Are there other minor issues. Actual Results: The button is no present. So I have no Script Phyton support. Expected Results: I want to try the button. Application kig (kededu) has no python scripting support, and a lot of minor issues. In this italian post - http://forums.gentoo.org/viewtopic.php?p=2056658 - motaboy explained me it depends about package boost. kig needs boost as a dipendence, but portage doesn't know that. Emerging boost and reemerging kdeedu solves the problem. In my attachment, I've joined a lot of output about compilation. I used two independent installations, 32-bit and 64-bit, on a laptop amd64.
Created attachment 50519 [details] bug-report
To summarize, python scripting support in kdeedu-3.3.2 works for you with boost-1.31.0 and 1.32.0 on amd-32bit, while it works only with boost-1.31.0 with amd64, right? Have you tried kdeedu-3.4.0_betas?
Created attachment 51229 [details] log output boost-1.32.0 works on amd64, too (kdeedu-3.x). Just 1.30.0, 32 bit, doesn't compile. Instead, on kdeedu-3.4.0_beta*, everything compile fine, but there is no python support.
> Instead, on kdeedu-3.4.0_beta*, everything compile fine, but there is no > python support. Well, you should have removed the --disable-kig-python-scripting option in the ebuild before trying...
Created attachment 51379 [details] log-output sgrunt... I'm not educated to check ebuilds before compiling. Now I've used dir portage-overlay to add python support. All ebuilds fail on compiling python scripting. I've attached the log output.
Yes, that's the same I was getting. Can you report the error to http://bugs.kde.org ? (only the compilation error is relevant, there's no need to attach the full logs) Thanks for your efforts so far.
http://bugs.kde.org/show_bug.cgi?id=99759
Hi, I'm the author of Kig. This bug is caused by boost.python changing their library name in boost 1.32. It does not appear in Debian because they provided a link for the old library name. However, the real fix is for me to adapt Kig's configure script to look for the new library name as well. I hope I will get that done in time for the next KDE release ( meaning I have to do it this weekend ).
UPDATE: I fixed it in KDE HEAD, can you test ? Preferably before the KDE 3.4 release in a few days..
Created attachment 51644 [details] good test output of Dominique's and gregorio's patches Now everything works fine. Thank you for your work. I've added a lot of output because I'm a noob, and I have to proof everything what I say.
Sorry. Everything goes fine on 32-bit, but on 64 I have this error: Making all in scripting In file included from /usr/include/python2.3/Python.h:8, from python_scripter.cc:20: /usr/include/python2.3/pyconfig.h:856:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/features.h:7, from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/include/g++-v3/x86_64-pc-linux-gnu/bits/os_defines.h:39, from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/include/g++-v3/x86_64-pc-linux-gnu/bits/c++config.h:35, from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/include/g++-v3/bits/stl_algobase.h:64, from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/include/g++-v3/bits/stl_tree.h:66, from /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/include/g++-v3/set:66, from ../objects/common.h:21, from python_scripter.h:21, from python_scripter.cc:18: /usr/include/gentoo-multilib/amd64/features.h:150:1: warning: this is the location of the previous definition /usr/include/boost/python/with_custodian_and_ward.hpp: In static member function `static PyObject* boost::python::with_custodian_and_ward_postcall<custodian, ward, BasePolicy_>::postcall(const ArgumentPackage&, PyObject*) [with ArgumentPackage = PyObject*, long unsigned int custodian = 0ul, long unsigned int ward = 1ul, BasePolicy_ = boost::python::default_call_policies]': /usr/include/boost/python/detail/caller.hpp:201: instantiated from `PyObject* boost::python::detail::caller_arity<1u>::impl<F, Policies, Sig>::operator()(PyObject*, PyObject*) [with F = boost::python::detail::member<Coordinate, ConicPolarData>, Policies = boost::python::return_internal_reference<1ul, boost::python::default_call_policies>, Sig = boost::mpl::vector2<Coordinate&, ConicPolarData&>]' /usr/include/boost/python/object/py_function.hpp:39: instantiated from `PyObject* boost::python::objects::caller_py_function_impl<Caller>::operator()(PyObject*, PyObject*) [with Caller = boost::python::detail::caller<boost::python::detail::member<Coordinate, ConicPolarData>, boost::python::return_internal_reference<1ul, boost::python::default_call_policies>, boost::mpl::vector2<Coordinate&, ConicPolarData&> >]'python_scripter.cc:576: instantiated from here /usr/include/boost/python/with_custodian_and_ward.hpp:88: warning: comparison is always false due to limited range of data type /usr/include/boost/python/detail/caller.hpp: At global scope: /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/tuple/detail/tuple_basic.hpp:291: warning: unused parameter 't1' /usr/include/boost/tuple/detail/tuple_basic.hpp:291: warning: unused parameter 't1' /usr/include/boost/tuple/detail/tuple_basic.hpp:291: warning: unused parameter 't1' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/include/boost/python/detail/caller.hpp:89: warning: unused parameter 'args_' /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/../lib64/libboost_python-gcc-mt-1_31.a(list.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/../lib64/libboost_python-gcc-mt-1_31.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[3]: *** [libkigpart.la] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 !!! ERROR: kde-base/kdeedu-3.4.0_beta2 failed. !!! Function kde_src_compile, Line 166, Exitcode 2 !!! died running emake, kde_src_compile:make !!! If you need support, post the topmost build error, NOT this status message. >>> md5 src_uri ;-) kdeedu-3.3.92.tar.bz2
solved recompiling boost-1.32.0
