SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is it a good idea to wait for an official 3.4 package set, I have had problems with 3.2 and 3.3 packages from Linuxpackages before.
Is Patrick waiting for 3.4.1?
Well, if you have had problems with third party packages, maybe its a good idea to wait for the official packages. If you are a bit adventuruous you can compile it yourself.
I haven't had any problems with the Linuxpackages packages so far. Only thing I've heard is that the packages don't support smtp (outgoing mail) authentication. But I don't use that anyway.
I compile a lot of my apps myself. But KDE just takes to damn long.
As mentioned, KDE isn't too hard too compile. The configure script is also helpful because it informs you of any missing dependencies and where to download them. I am actually using a version I compiled myself and it works like a charm.
If you have lots of memory, it's a good idea to pass the --enable-final option to ./configure. I've found it cuts the compile time down by 30-40%. I've got a 2GHz CPU and 512MB of RAM, and I can get most of KDE (the bits I want) compiled in about 3 hours.
(Apparently what --enable-final does is concatenate all the source files before compiling. This is supposed to create size-optimised binaries, but the decreased compile time is a far more interesting side effect!)
Does anyone have any last-minute advice before I attempt to install KDE 3.4 on a standard Slackware 10.1 distribution? When installing Slackware I chose the full package, whole nine yards, but I am afraid of breaking anything once I install KDE 3.4
So far I have downloaded qt-x11-free-3.3.4.tar.bz2 from trolltech and all the bz2 files from ftp.du.se/pub/mirrors/kde/stable/3.4/src (including the i18n file - what is this?)
I guess I'll go to runlevel 3 prior to doing anything, as to ensure no files are in use, but apart from that - any hints anyone?
Logout and login again to make these changes take effect..
4) Start compiling Qt:
Code:
cd $QTDIR
./configure -system-zlib -qt-gif -system-libpng \
-system-libjpeg -plugin-imgfmt-mng -thread -no-stl \
-no-xinerama -no-g++-exceptions
make
These options are the ones recommended in the KDE website.
Notice that you don't need to "make install" since you are already compiling inside the target dir.
5) Start compiling KDE. For every *.tar.gz file do:
Code:
tar xzf <packagename>.tar.gz
cd <packagename>
./configure
make
make install
You must install in the following order: 1) arts 2) kdelibs 3) kdebase. At this point you can already run KDE and see it working. Then compile and install the other packages as you need them. Remember to leave kdeaddons as the last to be installed.
It tooks several hours! You may try the --enable-final as Nobber suggested (if I knew that before...)
Originally posted by Haiyadragon I haven't had any problems with the Linuxpackages packages so far. Only thing I've heard is that the packages don't support smtp (outgoing mail) authentication. But I don't use that anyway.
I compile a lot of my apps myself. But KDE just takes to damn long.
Where'd you hear this? I'm having trouble with smtp if my firewall is enabled, but otherwise, it works fine.
Edit: I just tried running Thunderbird on TWM, and it doesn't work either. So my problem, at least, doesn't have to do with KDE smtp authentication.
People on linuxpackages and userlocal.com said they had trouble with it. Normal smtp works fine as long as no authentication is required.
Anyway, I'm back to KDE 3.3.2 from current. I ran into quite a few (minor) bugs and I decided I will wait for 3.4 to go current since 3.3.2 works great. But I think we might have to wait for 3.4.1.
Originally posted by Haiyadragon People on linuxpackages and userlocal.com said they had trouble with it. Normal smtp works fine as long as no authentication is required.
I'm trying to diagnose whether I have that problem. Is this only for KMail, or is it a general lack of support of SMTP-auth? I tried Thunderware in TWM and Failsafe, and it failed still, so it would seem to indicate that it's not a KDE problem.
Originally posted by apachedude I'm trying to diagnose whether I have that problem. Is this only for KMail, or is it a general lack of support of SMTP-auth? I tried Thunderware in TWM and Failsafe, and it failed still, so it would seem to indicate that it's not a KDE problem.
It should only be a problem in KMail. So something else is going on with your setup.
Originally posted by Haiyadragon It should only be a problem in KMail. So something else is going on with your setup.
Fixed it. I really want to try KMail, but I'm hanging onto Thundermail for now in case I'm ever stuck with Windows. Hopefully, when QT 4.0 comes out a port of KDE for Windows well too.
I haven't used Windows in months, but KDE on the Windows desktop could have a HUGE impact.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.