https://bugs.kde.org/show_bug.cgi?id=415918
--- Comment #9 from Maurizio Paolini <paol...@dmf.unicatt.it> ---
(In reply to Antonio Rojas from comment #5)
> (In reply to Maurizio Paolini from comment #4)
> > (In reply to Antonio Rojas from comment #2)
> > > Works fine here. Is your kig compiled with python 3?
> >
> > This is an interesting question: I *thought* my kig was compiled with
> > python3,
> > What I have now installed is the result with the latest git HEAD in a Fedora
> > 31 updated box.
> > an 'ldd /usr/bin/kig' does not show any reference to python libraries
>
> You need to look at ldd output for kigpart.so, the kig binary itself doesn't
> link to python
ok, I ran " ldd /usr/lib64/qt5/plugins/kigpart.so | grep python" and got
libpython2.7.so.1.0 => /lib64/libpython2.7.so.1.0 (0x00007f2d91c44000)
libboost_python27.so.1.69.0 => /lib64/libboost_python27.so.1.69.0
(0x00007f2d91c00000)
(After a "git pull; make; make install" of the kig project). I do not know
if this is the result of a messy situation: I actually loss control of the
status of the transition to python2.7.
I just tried to recompile from scratch and the output of cmake produces:
[...]
-- Found BoostPython: /usr/lib64/libpython2.7.so;/usr/lib64/libboost_python.so
[...]
so I guess that there is some reminiscence of python2
--
You are receiving this mail because:
You are watching all bug changes.
