Error Trying To Install Kiba-Dock on Ubuntu Gutsy 64
Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
for the plugins part (third one) when I got this error:
Code:
Making install in src
make[1]: Entering directory `/home/ryan/kiba-dock/kiba-plugins/src'
make install-am
make[2]: Entering directory `/home/ryan/kiba-dock/kiba-plugins/src'
/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -o liblauncher.la -rpath /usr/local/lib/kiba-dock/lib/kiba-dock -module -avoid-version -no-undefined launcher-plugin.lo -lxml2 -lakamaru -lrsvg-2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lfontconfig -lXext -lXrender -lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage -lX11 -lXfixes -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 liblauncher-type.la
gcc -shared .libs/launcher-plugin.o -Wl,--whole-archive ./.libs/liblauncher-type.a -Wl,--no-whole-archive /usr/lib/libxml2.so /usr/lib/libakamaru.so -lrsvg-2 /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libpangocairo-1.0.so -lXext -lXinerama -lXi -lXrandr -lXcursor -lXcomposite -lXdamage -lXfixes /usr/lib/libpango-1.0.so /usr/lib/libcairo.so /usr/lib/libfreetype.so -lz -lfontconfig -lpng12 -lXrender -lX11 -lm /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libglib-2.0.so -Wl,-soname -Wl,liblauncher.so -o .libs/liblauncher.so
/usr/bin/ld: ./.libs/liblauncher-type.a(launcher.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC
./.libs/liblauncher-type.a(launcher.o): could not read symbols: Bad value
collect2: ld returned 1 exit status
make[2]: *** [liblauncher.la] Error 1
make[2]: Leaving directory `/home/ryan/kiba-dock/kiba-plugins/src'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/home/ryan/kiba-dock/kiba-plugins/src'
make: *** [install-recursive] Error 1
The three packages to install after that gave similar messages. The first two were fine - kiba-dock and akamaru. Its a new (almost a week old now) Ubuntu Gutsy install (amd64). Other than this, about all I've done is compiz and other eyecandy like changing the theme and the panels, as well as media codecs. Anybody understand what that means, and more importantly, how I go about fixing it so that I can get kiba-dock to work?
What directory would that/those be? I tried with /usr for both as was being used in the other guide, but I don't really know enough about Linux directories to know what it is supposed to be. And I found the folder /usr/lib64, which I took as a good sign. I got the error message:
Quote:
Failed to locate Plugins at '/usr/local/lib/kiba-dock'
Please install the Plugins at '/usr/local/lib/kiba-dock' or use the '--plugin-path' command line parameter.
So I recompiled plugins by putting /usr/local/lib/kiba-dock in the <DIR> of the prefix tag and got the same thing.
The prefix that you want to install to. It defaults to /usr/local if not specified. Clean the kiba-plugins source tree and rebuild the package with -fPIC.
Code:
make distclean
CC="gcc -fPIC" ./autogen.sh --prefix=/usr
sudo make install
But, if you followed the instructions in that thread you linked to, you now have 64-bit libraries mixed in with 32-bit libraries in /usr/lib. The 64-bit libraries belong in /usr/lib64. You also have part of your kiba stuff in /usr and part in /usr/local. You really should follow the uninstall instructions and start over doing it correctly.
Code:
cd akamaru/ &&
./autogen.sh --prefix=/usr --exec-prefix=/usr --libdir=/usr/lib64 &&
sudo make install &&
cd .. &&
cd kiba-dock/ &&
./autogen.sh --prefix=/usr --libdir=/usr/lib64 &&
sudo make install &&
cd .. &&
cd kiba-plugins/ &&
CC="gcc -fPIC" ./autogen.sh --prefix=/usr --libdir=/usr/lib64 &&
sudo make install &&
cd .. &&
cd kiba-dbus-plugins/ &&
./autogen.sh --prefix=/usr --libdir=/usr/lib64 &&
sudo make install &&
cd ..
Last edited by weibullguy; 10-25-2007 at 11:28 PM.
Thanks so much! It works, just with a few glitches and settings I need to work out.
::::Edit::::
More glitches than I was noticing at first:
1. After reboot, a big white box with black outline appears at the end of dock. It goes away if I stop the dock and start it again, but is always there after reboot.
2. The Firefox launcher causes various problems. It started booting to address "0", so I changed the launch command from "firefox 0" to "firefox" to get that back. Then, as soon as I close Firefox, the dock closes. If I restart the dock, the firefox launcher is gone again.
3. The icons don't line up properly with physics turned on - they're all offset in slightly varying positions each time. Also with physics turned on, the icons don't auto-hide, just the dock.
4. I clicked the enable button for "Gnome Menu", but it doesn't appear.
5. I dropped the folder of all my music onto it after enabling stacks, and the music simply disappeared. It wasn't on the hard drive anymore, or on the dock. I even ran a search of the computer to find it, and there was nothing. Not a very pleasant error, although at least I still had most if not all on my Mac.
::::Edit Again::::
6. When I just opened Pidgin (the contact list, it was already running), the dock closed. Think that was the second or third time - knew I had been forgetting something.
Any help fixing any or all of the above would be greatly appreciated.
Last edited by rapsball4; 10-26-2007 at 02:14 PM.
Reason: Error Update
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.