QT 3.2b :-(

Andras Mantia amantia at freemail.hu
Sun May 18 16:30:31 BST 2003

Hash: SHA1

On Sunday 2003 May 18 16:04, Dirk Mueller wrote:
> On Sam, 17 Mai 2003, Andras Mantia wrote:
> > Well, I think I just switch back to QT 3.1.2 and recompile all the KDE
> > until this issues are fixed (or until KDE HEAD is not requiring QT 3.2).
> > :-( BTW, it seems that there is a BC issue between QT-COPY (the one after
> > the BC fix was committed) and QT 3.1.2, as kdeinit will not start if I
> > simply change back the libqt... link to the 3.1.2 one, and complains
> > about missing symbols.
> Qt 3.2 is backward compatible. if you compiled against 3.2 and then try to
> un against Qt 3.1, it will naturally fail.

Yes, I was stupid, and when I looked more closer to the error, I quickly 
realized that the new symbols cannot be present in 3.1.2....
> The other crashes you report are just simple bugs, they will be fixed soon.
> Maybe you can help by compiling k3b with debug support and valgrinding it,
> I'm sure you will find some problems.
I did it, but valgrind fails to work with my self-compiled 2.4.20 kernel with 
preemptive patch. And I was too tired and upset that everything is crashing 
in most unexpected places to work more on it. I put the PC to re-compile the 
whole KDE for QT 3.1.2 and went to sleep.
BTW, I reported a Konqui bug (#58607) regarded to random execution of items in 
the RMB menu in the sidebar. Well, it turned out that the bug also 
disappeared by switching back to QT 3.1.2. 

So, now I use QT 3.1.2, but I think after a few more days I will give a try to 
qt copy again. ;-)

> Dirk

- -- 
Quanta Plus developer - http://quanta.sourceforge.net
K Desktop Environment - http://www.kde.org
Version: GnuPG v1.2.1 (GNU/Linux)


More information about the kde-core-devel mailing list