LinuxQuestions.org - KDE 3.5.10 for slackware-13.1

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - KDE 3.5.10 for slackware-13.1 (https://www.linuxquestions.org/questions/slackware-14/kde-3-5-10-for-slackware-13-1-a-849525/)

Quote:

One thing I noted is a strange behavior - time to time - of a mouse. It runs out to an edge of a screen. Also a communication between a mouse and the desktop works not well as sometimes moves of mouse is interpreted as clicks.

This may be some kind of coincidence, but some time ago, when I was still using slackware-12.x with kde 3.5, I had problems with mouse behavior, similar to yours. I simply thought it was broken, so i changed it. Never had those problems again. (The device was a cheap "Manta", first optical mouse I had)

Yeah I also thought the same after I posted. I'll try a different mouse. That can be broken.

I forgot to mention that in order to use kdm you need to edit /etc/rc.d/rc.4 script.
Change the lines:

Code:

if [ -x /opt/kde/bin/kdm ]; then

  exec /opt/kde/bin/kdm -nodaemon

elif [ -x /usr/bin/kdm ]; then

  exec /usr/bin/kdm -nodaemon

fi

To:

Code:

if [ -x /opt/kde3/bin/kdm ]; then

  exec /opt/kde3/bin/kdm -nodaemon

elif [ -x /usr/bin/kdm ]; then

  exec /usr/bin/kdm -nodaemon

fi

After running kdm you have to choose "KDE" session type to log in.

I've been running a Slackware 13.1 64-Bit system with KDE 3.5.10 for about 8 months now, you can make a Slackware 13.1 64-Bit system running on KDE-3.5.10
By Using "menu selection" during the Slackware64 13.1 install and "DO NOT" installing any of the KDE packages, and "DO NOT" installing: QScintilla, attica, automoc4, phonon, qca, qca-cyrus-sasl, qca-gnupg, qca-ossl, qimageblitz, qt4, qtscriptgenerator, and Soprano from the l directory. Then proceed with the rest of the installation as normal.

After rebooting the machine, install the all the KDE 3.5.10 packages from Slam64 12.2 and arts, dbus-qt3, qca, qca-tls, qt3 from the l directory of Slam64 12.2. Reboot the machine, and issue a

Code:

xwmconfig

select the KDE desktop.

Code:

startx

I've been able to compile and run most programs from places like Slackbuild, although sometime I trouble figuring out if I need to use the Slackbuild 13.1 or 12.2 script.

Do you compiled that additional applications as 64 bit or as 32 bit using 'multilib'?

Quote:

Originally Posted by liuguobiao (Post 4190925)

haha , So , lots of website ( for example facebook, youtube ,even the website which to change password in google code) are blocked in my country .So sad It made me ... But linuxquestions.org has escaped .

ennorie , Thanks for your link . Although it's remain 5~6 hours to download the file ...

Don't let it keep you sad, it's not worth it.
It will change in time as the old guard slowly die out, just like it did in Russia.
And as technology becomes even more influential on our daily lives, it'll make it harder to censor communication.
The Internet has already made it possible for you to communicate freely with the rest of the world.
When I was growing up behind the iron curtain in the 70s before I defected, the only (one way only) communication was the Voice of Free Europe which I'd listen to at night on short wave radio pressed to my ear and reception was really bad and breaking up all the time.
So just live you life to its fullest and don't let politics depress you.
Oh yeah, and don't get caught ;)

Why not add gtk-qt-engine??
So gtk application can cute like kde app :)

Is there a 64bit version available? I get "Could not start kstartupconfig" when I try to start it.

I'm going to try Stragonian's method, installing from the slamd64 files, and see if that works. Not very hopeful, but it's worth a shot...

You might run into some automake problems: KDE 3.5.x for Slackware

Some questions to Stragonian and alekow:

Is there a place online to download your build scripts? My ISP prohibits file sharing in any manner. I can't use torrents. :(

3.5.10 needs many patches for gcc 4.x, python 2.6, etc. Do you have those patches available somewhere?

I see the link above for the large tar from rapidshare, but does that download include build scripts and patches?

Regarding do not install QScintilla, attica, automoc4, phonon, qca, qca-cyrus-sasl, qca-gnupg, qca-ossl, qimageblitz, qt4, qtscriptgenerator, and Soprano from the l directory --- does that mean when building too?

Thanks.

There is a script for downloading the source code with all patches included. You can find it in the tar archive. If you want I can send it to you by email. Just send me your email adress by PM.
As for Qscintilla and others - i didn't remove them at all. I just didn't install kde/ series. To be honest - I don't really know if it's a good approach.

Have you (or anybody caring to respond) tried building and running 3.5.10 in Current/13.37?

No, not yet. I don't think i'll have enough time in the nearest future. If I try i'll let you know.

I have been making good progress building 3.5.10 on 13.1.

I ran into a problem building amarok. How did you do that?

The amarok configuration is looking for ruby 1.8 and not 1.9. Did you temporarily uninstall 1.9, build and install 1.8 for 13.1? Did you build a special 1.8 package that does not overwrite 1.9 files?

Edit: kdebindings also fails to build, with error messages about ruby.

Lastly koffice does not build, but I notice you don't offer any koffice package. Were you able to build koffice?

Thanks for any help.

Did you use KDE.SlacBuild? Try building every slackbuild manually - I did it that way - just remember to follow package building order found in the KDE.SlackBuild. It's much easier to track errors if you do so. In case of error just paste the error output here - I'll try to help. It's very unlikely that I've forgot to include any patch, but it's possible...

Or maybe...
How did you download the source? Did you use my script? Did you have 'kde_source.diff' and 'l_source.diff' in directory which contained 'download_source.sh' file?
And finally there is another possibility. I just thought that there is a bug in my script. If you try running it from a directory different from the one that it actually is in, you will run into problems with patching.

For example: if your files are in /some_path/directory/ and your `pwd` is /some_path/ and you try to run the script by using a command

Code:

sh directory/download_source.sh

You'll end up with an error saying:

Code:

patching libraries

cat: /some_path/l_source.diff: No such file or directory.

Hmm...  I can't seem to find a patch in there anywhere.

while it's obvious, that the file is located in /some_path/directory/l_source.diff

Sorry for that - I'm a beginner at scripting ;-)

EDIT:

All right - now I know what's the problem. As I stated in the other thread:
http://www.linuxquestions.org/questi...7/#post4307373

There is one thing I forgot - before you build kdebinding you have to create a link in /usr/lib/ruby/1.9.1/i486-linux/ which points to /usr/include/ruby-1.9.1/ruby.h