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/)

I'm having no problems with building any of the other packages. Just kdebindings, amarok, and koffice. No problems applying the patches.

Yesterday I had already tried the sym link trick but that did not work. Perhaps I did not create the link correctly. I'll try that again.

After both kdebindings and amarok failed to build, I uninstalled the ruby-1.9.1 package and then built and installed the 1.8.7 package. That solved the problem of building amarok, but kdebindings keeps failing with an error reference about Qt.cpp and Qtruby.

Code:

make[5]: Entering directory `/dev/shm/kdebindings-3.5.10/qtruby/rubylib/qtruby'

/bin/sh ../../../libtool --silent --tag=CXX  --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../smoke -I/opt/kde3/include -I/opt/kde3/lib/qt-3.3.8b/include -I.  -I/usr/lib/ruby/1.8/i486-linux  -DQT_THREAD_SUPPORT  -D_REENTRANT  -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -march=i486 -mtune=i686 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common  -MT Qt.lo -MD -MP -MF .deps/Qt.Tpo -c -o Qt.lo Qt.cpp

Qt.cpp: In function 'VALUE pretty_print_qobject(VALUE, VALUE)':

Qt.cpp:1272: warning: too many arguments for format

Qt.cpp: In function 'VALUE dumpCandidates(VALUE, VALUE)':

Qt.cpp:2611: error: 'rb_str_catf' was not declared in this scope

make[5]: *** [Qt.lo] Error 1

The kdebindings error message seems related to one of the patches. I will be trying again today.

BTW, for anybody interested, I found some libpng patches for both digikam and gwenview. I can build both in 13.1.

Huh :-)

So, one more try!
There are TWO ruby.h header files:
- /usr/include/ruby-1.9.1/ruby.h,
and
-/usr/include/ruby-1.9.1/ruby/ruby.h

The first one includes the other:

Code:

#include "ruby/ruby.h"

As i mentioned before you got to have a symlink /usr/lib/ruby/1.9.1/i486-linux/ruby.h pointing to /usr/include/ruby-1.9.1/ruby.h. BUT I forgot another thing: there is still need to create a SECOND symlink

Code:

/usr/lib/ruby/1.9.1/i486-linux/ruby -> /usr/include/ruby-1.9.1/ruby

to make the above mentioned #include possible.

I hope that was it :-)

Create those symlinks, get rid of ruby 1.8 an compile. It has to be alright now.
Compiling kdebindings with ruby-1.8 fails because of the patches applied (for example Qt_cpp2.diff), which I had to apply due to differences in ruby syntax between 1.8 and 1.9 versions.

As for compilation of koffice, you'll have to find your own solution. I thought it would be pointless, 'cause I wouldn't even use it anyway. I mean - who needs it at all?

Wish you luck. By the way - thanks for testing!

Yay! Looks like both sym links do the trick. kdebindings finally compiled. I rebuilt amarok again too with no errors. :D

I'm not concerned about koffice. Might be nice to have some of the support apps like kivio or krita but LibreOffice will do fine for the most part.

I have been building all of this on a remote chroot system. Next big test is actually installing the packages and testing. Might be a good idea to do a clean install of 13.1 in the chroot and run the build process one more time. :)

Quote:

Might be a good idea to do a clean install of 13.1 in the chroot and run the build process one more time.

Yes, definitely. Or, if you use 32-bit system, you may as well test my packages as they were built exactly the same way (clean chroot environment).

If you are interested, here are an older KDE3 variant (for Slackware 13.0), which I built myself:

http://ftp.darkstarlinux.ro/slackware/source/kde3*

What is so special about this version? I created some patches for KDE3, to be installed and work in parallel with KDE4.

So, the installation is in '/opt/kde3' and KDE3 uses '/etc/kde3' and '~/.kde3', etc. ...

I think maybe it will be useful for something ... :)

I have quite a collection of patches. :) alekow provided more. After building the main KDE3 suite packages I hunted for more patches to build third party KDE3 packages. I can build Amarok, Digikam, Gwenview, K3B with full multimedia support, Kaffeine, gtk-qt-engine, K9Copy, Knemo, and KTorrent in 13.1. I'm curious to try again in 13.37, but I might just wait for the next version of Trinity.

Many of these patches have been merged into the Trinity project, but I need to submit those that haven't. For example, many of the libpng 1.4 patches need to be merged into Trinity.

I will browse through your files and see what patches I might be missing. I'm amazed and happy to see so many people around the world keeping KDE3 alive and well. To paraphrase that infamous quote from Mark Twain, reports of KDE3's death are greatly exaggerated. Right now the Trinity developers are making significant strides converting to a cmake build system and providing hooks into QT4. With those changes Trinity should be around a long time. Getting 3.5.10 working on 13.1 buys me time until the next version of Trinity is ready. I'll continue to tinker with KDE4, but I don't like all the cruft that is enabled by default. Xfce is too limited and is becoming more like GNOME. KDE3 had the right amount of configurability for a desktop environment.

There is one error in qca1.SlackBuild. The last line should be changed to:

Code:

makepkg -l y -c n ../qca1-$VERSION-$ARCH-$BUILD.txz

I've found some time ;-) and right now I'm revisiting the source to prepare it for compilation on slackware-13.37.

Quote:

right now I'm revisiting the source to prepare it for compilation on slackware-13.37.

I plan to test when 13.37 goes official.

I can't compile a full Amarok package in 13.1. The package builds and and the binaries seem to function. Yet none of the locale or /usr/share/doc/HTML help files are part of the package.

I don't have this problem in 12.2. I'm guessing then the problem is with the patches for gcc 4.4 or ruby. Probably the gcc 4.4 patches somehow trip the makefiles in those sections.

The Arch folks seem to have patches for ruby, but I can't find them anywhere. Just numerous references to the patches.

Any ideas?

check under /opt/kde3

Quote:

check under /opt/kde3

Check for what? The locale and HTML files? No, they are not part of the package or in the temporary location where the package is built. The files are not being built into the package.

Then - check in my package. Seems fine here.

Quote:

Then - check in my package. Seems fine here.

Link?

I'll check but comparing contents of packages won't help me debug why the package is incomplete here. . . .

Quote:

Link?

http://www.linuxquestions.org/questi...5/#post4187291
http://www.linuxquestions.org/questi...5/#post4188934

Quote:

I'll check but comparing contents of packages won't help me debug why the package is incomplete here. . . .

Hmmm... I think it MAY help, because you probably used the same source (or didn't you?) and it may also tell you that it's not a problem with any of the patches used. Maybe you should just use a truly clean environment? Fresh chroot install maybe?

Is there a way to download only the Amarok package?

BTW, I have a copy of your full build tree. I'm using the same patches as you.

In my build environment I replaced autoconf 2.65 with 2.63 and automake 1.11.1 with 1.10.1 from Slackware 12.2. Amarok then built completely. Which versions of the autotools did you use?