SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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.
make: 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: *** [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.
So, one more try!
There are TWO ruby.h header files:
The first one includes the other:
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
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?
Yay! Looks like both sym links do the trick. kdebindings finally compiled. I rebuilt amarok again too with no errors.
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.
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.
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?