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.
Greetings! I am trying to build AlienBOB's KDE packages (4.8.1) for the stable 13.37 slackware release. This is a multi-lib setup. I was able to build all of the packages in deps/ with no problems. However, the main KDE.SlackBuild is failing at the same spot. I'm a bit stumped at the moment and I'm not sure if the culprit is the multi-lib setup. Here's the code where it fails:
Code:
[ 98%] Building CXX object dolphin/src/CMakeFiles/kdeinit_dolphin.dir/panels/search/searchpanel.o
[ 98%] Building CXX object dolphin/src/CMakeFiles/kdeinit_dolphin.dir/panels/terminal/terminalpanel.o
Linking CXX shared library ../../lib/libkdeinit4_dolphin.so
CMakeFiles/kdeinit_dolphin.dir/panels/information/phononwidget.o:(.data.rel.ro._ZTV19EmbeddedVideoPlayer[vtable for EmbeddedVideoPlayer]+0x38): undefined reference to `Phonon::VideoPlayer::event(QEvent*)'
collect2: ld returned 1 exit status
make[2]: *** [lib/libkdeinit4_dolphin.so] Error 1
make[1]: *** [dolphin/src/CMakeFiles/kdeinit_dolphin.dir/all] Error 2
make: *** [all] Error 2
[ 0%] Built target konq_automoc
[ 2%] Built target konq
Generating moc_konq_sound.cpp
[ 2%] Built target konq_sound_automoc
Scanning dependencies of target konq_sound
[ 2%] Building CXX object lib/konq/CMakeFiles/konq_sound.dir/konq_sound_automoc.o
Linking CXX shared module ../konq_sound.so
[ 2%] Built target konq_sound
[ 2%] Built target kded_favicons_automoc
[ 2%] Built target kded_favicons
[ 2%] Built target kdeinit_dolphin_automoc
[ 2%] Built target dolphinprivate_automoc
[ 12%] Built target dolphinprivate
Linking CXX shared library ../../lib/libkdeinit4_dolphin.so
CMakeFiles/kdeinit_dolphin.dir/panels/information/phononwidget.o:(.data.rel.ro._ZTV19EmbeddedVideoPlayer[vtable for EmbeddedVideoPlayer]+0x38): undefined reference to `Phonon::VideoPlayer::event(QEvent*)'
collect2: ld returned 1 exit status
make[2]: *** [lib/libkdeinit4_dolphin.so] Error 1
make[1]: *** [dolphin/src/CMakeFiles/kdeinit_dolphin.dir/all] Error 2
make: *** [all] Error 2
kdebase failed to build.
multilib could be a possible culprit, check out this info from the slackbuilds.org FAQ, this has always worked for me when I have had compiling errors with multilib.
I have problems compiling with my unofficial and unsupported multilib setup.
If you are using multilib packages from somewhere and also have some 32bit packages installed, then you might run into problems with the build process trying to link 32bit libraries instead of 64bit libraries. If this occurs, it can probably be solved by placing the following line:
LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \
after the lines for CFLAGS and CXXFLAGS passed to the configure script. In other words, make it look something like this:
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \
./configure \
Beyond that, you are on your own. This is an unsupported setup.
multilib could be a possible culprit, check out this info from the slackbuilds.org FAQ, this has always worked for me when I have had compiling errors with multilib.
I have problems compiling with my unofficial and unsupported multilib setup.
If you are using multilib packages from somewhere and also have some 32bit packages installed, then you might run into problems with the build process trying to link 32bit libraries instead of 64bit libraries. If this occurs, it can probably be solved by placing the following line:
LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \
after the lines for CFLAGS and CXXFLAGS passed to the configure script. In other words, make it look something like this:
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \
./configure \
Beyond that, you are on your own. This is an unsupported setup.
I have seen that in the past and I have modified SlackBuilds with success. However, since this is using cmake, I'm not sure how to go about. I already see "/usr/lib${LIBDIRSUFFIX}" in parts of the script which could rule that out.
Alienbobs 4.8 package isn't intended for the stable release, are you aware of that? There are incompatible packages, and if you do desire to run it on 13.37, then you will have to upgrade some of the packages manually.
From Aliens page
Quote:
Please note that my own KDE packages have been compiled on Slackware-current. There has been an incompatible update to slackware-current recently (the glibc package) which will cause run-time errors if you attempt to start these KDE programs in Slackware 13.37. If you consider using KDE 4.8.1 on one of Slackware’s earlier (stable) releases, then you have no other option than to compile packages yourself. I have written down the guidelines in another blog post..
I think it could be a problem with Qt and phonon.
Check if in /usr/lib/qt/lib (or /usr/lib64/qt/lib if you have a 64 bits system) you have symbolic links pointing to an older version of phonon.
Please let me/us know if you succeed in compiling 4.8.1 for 13.37.
Knightron, yes I am aware of that. This is why I am building from source as he suggested. I already upgraded the mesa package as suggested on his documentation.
fgcl2k, I removed the old qt-compat32 package that was built with the old qt. I'm running the script again. I'll report back later.
Dang it! Nope, still fails at the same spot. I rebuilt the phonon packages just in case and the script still fails. I'm thinking that multilib may be the culprit, but I don't know for sure. Maybe someone can try to build it on a clean system (no multilib). I'll keep looking at my list of compat32 packages and see if anything sticks out as a problem.
Dang it! Nope, still fails at the same spot. I rebuilt the phonon packages just in case and the script still fails. I'm thinking that multilib may be the culprit, but I don't know for sure. Maybe someone can try to build it on a clean system (no multilib). I'll keep looking at my list of compat32 packages and see if anything sticks out as a problem.
I had the same problem with version 4.8.0. I checked in /usr/lib64/qt/lib and noticed that the symbolic links were pointing to the original version of phonon (the one installed with 13.37). I removed them and created them manually pointing to the new version of phonon. Then I compiled the last two packages in 'deps' with the Slackbuild without problems. I did not restart deps from the beginning.
Last edited by fgcl2k; 03-08-2012 at 11:55 AM.
Reason: Fix
I had the same problem with version 4.8.0. I checked in /usr/lib64/qt/lib and noticed that the symbolic links were pointing to the original version of phonon (the one installed with 13.37). I removed them and created them manually pointing to the new version of phonon. Then I compiled the last two packages in 'deps' with the Slackbuild without problems. I did not restart deps from the beginning.
Hmm...phonon was not installed before building the new packages. I finally gave up and just used Alien's packages on my slackware-current netbook. Took it for a spin long enough. Very nice desktop and definitely feels snappier. I did go back to xfce though. Thanks for your help.
just so this is documented here. I am running (and writing this from) KDE 4.8.1 with Slackware 13.37 multilib setup compiled from source. Previously I was running 4.8.0 (compiled from source) and upgraded everything (except extragear:calligra) successfully yesterday. Somehow Calligra didn't update and threw out errors that I haven't had a change to troubleshoot (I am thinking may be it just needs newer versions of slackware packages).
To be clear, as I was running 4.8.0 before this and noticed that only akonadi and phonon-gstreamer (both deps) were updated with 4.8.1. I just upgraded both of those and than ran the kde slackbuild.
I am not sure if this would be relevant here but I'm using the latest gstreamer, gst-plugins-base, gst-plugins-good and mesa compiled using stock Slackware build scripts.
I am hesitant to post this, as this thread initiated last month, but I am also building AlienBOB's KDE 4.8.2 on a stock 13.37 system. I am also hesitant because the original poster said that he'd build deps with no issues, however I started noticing some in deps. When I went to build phonon-gstreamer I first had issue, phonon-xine still had issue, did some searches in google, and found some answers that seemed to point toward old/bad header files from phonon, I thought it odd, but ok, I had both /usr/include/phonon and /usr/lib/qt/include/phonon, not being the most brilliant bulb in the pack, and not wanting to search endlessly for why I just renamed /usr/lib/qt/include/phonon to /usr/lib/qt/include/phonon.aside and symlinked /usr/include/phonon to /usr/lib/qt/include, and all built. As that took until the wee hours of the AM I went to bed to tackle kde when I got up. kdelibs failed with the error listed above and that's how I found this thread. Reading through it and remembering last night I got it in my head that somehow I could have a phonon problem, so I started digging and looking, and I did indeed have libphonon.so.4.4.0 in my /usr/lib/qt/lib folder and ofcourse it was also symlinked in /usr/lib. Now as I recall phonon was supposed to be disabled in the qt build, but for some reason my qt build included libphonon.so.4.4.0, (and a QtWebKit so with a changing number when I rebuilt it, but that's another post/issue), so I manually removed it, symlinked the one in user which is the 4.6.0 and kdelibs built fine.
I am hesitant to post this, as this thread initiated last month, but I am also building AlienBOB's KDE 4.8.2 on a stock 13.37 system. I am also hesitant because the original poster said that he'd build deps with no issues, however I started noticing some in deps. When I went to build phonon-gstreamer I first had issue, phonon-xine still had issue, did some searches in google, and found some answers that seemed to point toward old/bad header files from phonon, I thought it odd, but ok, I had both /usr/include/phonon and /usr/lib/qt/include/phonon, not being the most brilliant bulb in the pack, and not wanting to search endlessly for why I just renamed /usr/lib/qt/include/phonon to /usr/lib/qt/include/phonon.aside and symlinked /usr/include/phonon to /usr/lib/qt/include, and all built. As that took until the wee hours of the AM I went to bed to tackle kde when I got up. kdelibs failed with the error listed above and that's how I found this thread. Reading through it and remembering last night I got it in my head that somehow I could have a phonon problem, so I started digging and looking, and I did indeed have libphonon.so.4.4.0 in my /usr/lib/qt/lib folder and ofcourse it was also symlinked in /usr/lib. Now as I recall phonon was supposed to be disabled in the qt build, but for some reason my qt build included libphonon.so.4.4.0, (and a QtWebKit so with a changing number when I rebuilt it, but that's another post/issue), so I manually removed it, symlinked the one in user which is the 4.6.0 and kdelibs built fine.
Thank you for sharing this. I just ended up giving up on the issue. Building kde and its dependencies take forever and a day. I did try it out on Current and it is a very, very nice desktop. However, it's still a memory hog if you don't have the hardware. I've been pleased with XFCE but I do like to try KDE from time to time.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.