New subject: [SLE] qt bindings crocked

26 Dec 2002

      I'm having some problems with my python
qt bindings setup on SuSE 8.1

A python program like this

	import sys
	from qt import *
	# create application object
	myApp = QApplication(sys.argv)

segfaults when it gets to creating the QApplication.

I have qt 2.3.2 and qt 3.0.5 installed. There is a qt2 symlink
and a qt3 symlink.

I'm using Python 2.2.1

Essentially my setup is an out-of-the-box clean install of
SuSE 8.1 - I selected python and the qt bindings using YAST2, so
it should all "just work".

Am I missing something like a QTDIR environment variable? I've
tried exporting both QTDIR as /usr/lib/qt2 and QTDIR as
/usr/lib/qt3. I get the same seg fault.

Or is it some problem with versions of qt?

Any suggestions?

I should also point out that there is something fishy
about my qt environment generally as programs like
Knights find unresolved library calls at runtime.

The rpm of Knights 0.5.6 for SuSE 8.0 from the Knights website
gives the following runtime error :

knights: relocation error: knights: undefined symbol: __ti7QWidget

In the same way, previously a previously working version
of Quanta Gold also give runtime errors.

As far as I can recall, I had none of this trouble with SuSE 8.0

- Ken

qt bindings crocked

Kenneth Payne

James Oakley

tags

participants (2)