Attention when upgrading to qt-3.3.4-i486-1
I noticed that when upgrading from qt-3.3.3 to qt-3.3.4 suddenly all my eye candy in KDE disappeared. When I tried to recompile programs using the new qt version, './configure' would abort saying:
Code:
checking if UIC has KDE plugins available... http://amarok.kde.org/wiki/index.php...s_without_aRts So, basically this new qt package is flawed and I would recommend all of you to wait until the next package comes out, or you could recompile qt yourself but don't forget to include the -thread flag if you do... |
thanks for the warning.
egag |
Quote:
see the qt.SlackBuild for qt-3.3.4-i486-1 ftp://ftp.slackware.no/pub/linux/sla.../qt.SlackBuild I think the problem is elsewhere |
I'm I the only one having this problem or are you also experiencing it? Could be good to know that I'm not alone...
|
Hey everyone,
Maybe its me, but... what am I suppose to see wrong with upgrading to qt 3.3.4 ? (and yes, I read the links, but they don't mean much to me. I can compile programs, but if theres problems, well.... I'm just stuck - thats one of the things I want to learn about later this year.) I did it via swaret (upgrade to qt-3.3.4) - and everything looks normal. qtconfig comes up and it says ver-3.3.4., everything looks normal, etc. What should I be looking for / expecting ? I do have qt-3.3.3.tgz sitting in my root directory just in case. This thread kinda got me on edge, but so far so good. -tw |
OK, I upgraded my version of QT to 3.3.4 and I lost all of my eye candy as well. Sooooo, I reverted back to the previous version and all is well. Is there a way to upgrade to 3.3.4 and AVOID losing the eye candy?:confused:
|
Dear god, no need to recompile anything!
Just do this : telinit 1 login as root # removepkg kdelibs # cd <to downloaded kdelibs 3.4 dir> # installpkg kdelibs*tgz Thats all. If u use packaged kde, the qt on ur sys and qt version againt which package was compiled must match. Hence, to avoid all this hassle, first update to qt-3.3.4 and then update to kdelibs-3.4.0 Hope this helps... Rohan Dhruva. |
Quote:
|
Did my upgrade from Slack's /current files and everything is just fine, no problems at all.
|
Ok kids, I have all these updates KDE 3.4.0 the QT you are discussing and also the X11 6.8.2 upgraded just now.
FTP all the files you want to upgrade from the slackware site using gFTP and then save all the files in a separate directory, Then the best and most fun part of all........use this command in the directory you have all the tgz files to upgrade. type "upgradepkg *.tgz" and it will uninstall allth old pkgs and install the new ones and then all you need to do is reboot the system and you will be using all the latest and greatest from the slackware suite. I love Slackware, I am 3 weeks old into Linux and I can not even think of going back to that other os. My new Tag for this Windows is not a program, it's a virus. Once you get it, you can't get rid of it. Solution : Linux Anti Virus. Anyways all you other Slack users This tip is provided to you all for the BEST Version / Distro to hit the world. Slackware. |
ok so we can say that the slackware packages are safe so if you haven't already upgraded due to fear raised on this thread then belt away, you'll like the new KDE.
Also, when you upgrade there is no need to reboot your system, just exit and restart X. (For people on runlevel 3 just exit and enter startx. For those on runlevel 4 hit control+alt+backspace to restart X.) |
Quote:
I will never go back to that Win Thing, it's more a loss than anything else. Linux Rocks, and Slackware is my Fave Distro. |
Oh and there is no need to go and download the whole ftp server just do upgrade. In the slackware current/extras is slackpkg. Its what I used and it works great.
|
Dude, every slacker knows about stuff like swaret, slapt-get, slackpkg, slackgrade. Is there any need to repeat it ?
IMO, if someone prefers wget && upgradepkg, its quite logical as automated tools can break boxes.. Rohan. |
Some new Slackers may not know about slackpkg. Never hurts to let them know about it. If you already know about it, great. For those who didn't, know they do.
The only way slackpkg will break your system is if you blindly allow it to overwrite you config files without checking things out. |
All times are GMT -5. The time now is 10:10 AM. |