FS#6673 - qtiplot 0.8.9-1: needs recompile due to new python version

Attached to Project: Arch Linux
Opened by Niklas Volbers (nv) - Wednesday, 21 March 2007, 18:34 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 30 January 2008, 18:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Damir Perisa (damir.perisa)
Architecture All
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

qtiplot still tries to use python 2.4
This task depends upon

This task blocks these from closing
 FS#6280 - Packages need rebuild after python upgrade 
Closed by  Roman Kyrylych (Romashka)
Wednesday, 30 January 2008, 18:35 GMT
Reason for closing:  Fixed
Comment by Damir Perisa (damir.perisa) - Sunday, 09 September 2007, 11:24 GMT
qtiplot: has to wait for qt4 to be updated... the version that still works with qt3 does not compile any more

In file included from src/application.h:10,
from src/PythonScripting.cpp:24:
src/plot3DDialog.h:69: error: expected `:' before 'slots'
src/plot3DDialog.h:70: error: expected primary-expression before 'void'
src/plot3DDialog.h:70: error: ISO C++ forbids declaration of 'slots' with no type
src/plot3DDialog.h:70: error: expected ';' before 'void'
In file included from src/PythonScripting.cpp:24:
src/application.h:117: error: expected `:' before 'slots'
src/application.h:118: error: expected primary-expression before 'void'
src/application.h:118: error: ISO C++ forbids declaration of 'slots' with no type
src/application.h:118: error: expected ';' before 'void'
src/PythonScripting.cpp: In member function 'virtual QVariant PythonScript::eval()':
src/PythonScripting.cpp:498: warning: dereferencing type-punned pointer will break strict-aliasing rules
src/PythonScripting.cpp:509: warning: suggest parentheses around assignment used as truth value
make: *** [../tmp/qtiplot/PythonScripting.o] Error 1
==> ERROR: Build Failed. Aborting...
Comment by Brice (bricem13) - Tuesday, 13 November 2007, 19:26 GMT
qt4 is here! please rebuild!

regards, Brice
Comment by Damir Perisa (damir.perisa) - Tuesday, 13 November 2007, 20:35 GMT
qtiplot 0.9 will be soon in testing (deps are prepared) - it depends on pyqt>=4 and this is still work in progress
Comment by Damir Perisa (damir.perisa) - Monday, 19 November 2007, 01:27 GMT
0.9 is now in testing (x86_64, i686 soon too)

new dependency muparser (extra) (now external lib used)

works fine now with qt>=4 which is also in testing now

bug will close when qt>=4 moves out of testing
Comment by Martin (dante) - Tuesday, 27 November 2007, 13:06 GMT
Isn't it possible to build an additional static version of qtiplot, which could reduce dependencies problems?
Comment by Damir Perisa (damir.perisa) - Tuesday, 27 November 2007, 16:29 GMT
what do you want to build static into qtiplot?

it may reduce dependencies but it will increase the size of binary.

what is your "dependencies problem" you are speaking?
Comment by Martin (dante) - Tuesday, 27 November 2007, 17:25 GMT
At the moment it is not possible to use qtiplot 0.9 in the non testing branch. Version 0.8 wasn't/isn't usable too (makepkg with errors). When I download the static version from soft.proindependent.com/qtiplot.html I can use qtiplot without problems. So a suitable PKGBUILD would be nice.
Comment by Damir Perisa (damir.perisa) - Tuesday, 27 November 2007, 21:18 GMT
qtiplot 0.9 depends on qt>=4 and pyqt>=4 ... and this is going to be in arch - it is in testing now, thats why qtiplot is not in extra but testing for now. the one in extra is broken, i'm aware of this. if you need qtiplot, get it and all its dependencies from testing. they will be moved to extra once qt and pyqt >=4 is moved too.

if you want to use the static version, use ABS to make one. i will not provide one officially.
Comment by Martin (dante) - Tuesday, 27 November 2007, 22:10 GMT
I tried to build qtiplot for my own, but the adjustment of the *.pro file is horrible.
Comment by Damir Perisa (damir.perisa) - Tuesday, 27 November 2007, 22:16 GMT
yes it is :) - their building system instructions, especially 0.7.x up to 0.8.9 are horrible. for 0.9 it is a little bit better, but not really useful. but if you try to build 0.8.9, you will quite for sure fail with our newest pkgs (gcc,qt3,...).

if you do not like getting pkgs from testing (you do not need to get testing as main repo, just do a -S testing/qtiplot) you can just make a PKGBUILD that downloads the static version from the website instead of getting the source and building it.

what is your reason of not wanting qtiplot from testing?

by the way: liborigin is built statically now in qtiplot 0.9 still, because it does not like the latest lib we have... i hope they will make it work in 1.0
Comment by Martin (dante) - Wednesday, 28 November 2007, 06:52 GMT
OK, I installed qtiplot and its dependencies from testing. But I get following error on startup:

qtiplot: symbol lookup error: qtiplot: undefined symbol: _ZN13QwtPlotPicker16staticMetaObjectE
Comment by Damir Perisa (damir.perisa) - Wednesday, 28 November 2007, 10:05 GMT
i686?

i'm working with x86_64 here and it works fine... i will check the i686 pkg when i come home today.
Comment by Damir Perisa (damir.perisa) - Wednesday, 28 November 2007, 11:04 GMT
hmm... i just tested it with i686 pkg and it works fine for me. are you -Suy?
Comment by Damir Perisa (damir.perisa) - Wednesday, 28 November 2007, 11:05 GMT
try installing glib2 2.14.3-1 from testing
Comment by Martin (dante) - Wednesday, 28 November 2007, 18:39 GMT
I updated everything from the testing branch and it worked well.
Comment by Roman Kyrylych (Romashka) - Wednesday, 30 January 2008, 17:19 GMT
can this be closed now?
Comment by Brice (bricem13) - Wednesday, 30 January 2008, 18:33 GMT
Yeah!

Brice

Loading...