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.
Hey guys just wondering what way you guys recogmend installing HAL and DBUS on slack 10.2? I tried downloading the source for each, but DBUS didn't seem to install eveything as pgk-config would complain about a missing package when I tried installing HAL.
My goal is to get HAL,DBUS, and powersave installed on my laptop, I fell short of that goal a few hours ago as I could get HAL running, then when trying to compile powersave, pkg-config would complain about missing dbus-1 or somthing. Also that was when I used HAL and dbus packages from linuxpackages.com.
I had troubles compiling hal from source on a stock 10.2 system. Rather than slog it out, I did the easy fix; grabbed the hal, dbus and libcap packages from Freerock Gnome. The packages on linuxpackages.net didn't work for me.
Right, I had compiled 2.6 before i nuked it also I am not familiar with Freerock Gnome. I mostly prefer KDE, or does this not matter? Did you just install Freerock, or did you extract HAL and dbus from the package?
Thanks for chiming in - it's nice to know the dropline devs are hanging around.
I wasn't aware of that requirement when I was trying to build HAL and DBus. I didn't really spend time screwing with it, knowing that your (or FRG's) packages "just work". You've provided inspiration to give it another whirl, thanks!
Yes, the 2.4 headers are always installed, even if you are using 2.6.
My understanding of this is a little sketchy, but as far as I know, it installs the 2.4 headers because the headers have to match the kernel version that glibc was compiled against. So while you might be using a 2.6.x kernel, your glibc packages are still compiled against the 2.4 kernel.
I may be off base on that though, so anyone feel free to correct me, as I have always wondered about this myself, and this was my best understanding of the situation.
As for DBUS, I to used the LinuxPackages.net package and could not get it working, though I never actually tried as such. I just know that after the package installation, there were still DBUS errors when XFCE started. That is about the depth of my experimentation with this, I have no need for it myself.
MS3FGX - That's what I've always heard as well. Though I build my own custom kernels, I typically keep Slack's 2.6 headers from "/testing" on-hand for just the HAL package. I just upgradepkg back to the 2.4 headers after building HAL (It's best to keep the 2.4 headers unless you absolutely need the 2.6 headers).
j79zlr is correct. It would probably be a good idea to use dbus-0.50. We currently ship dbus-0.50 and hal-0.5.5.1 with Dropline GNOME 2.12.2 (for compatibility reasons). I think that GSB/Freerock GNOME does the same.
One thing that has only lightly been touched upon here is the udev situation. Depending on what you want to do with HAL, you may also need to update your udev package. Please see the following Dropline and GSB/Freerock mailing lists for details:
after much frustration with failure to make hal work with kde, i've found out that gware's hal and dbus slackbuilds works with slack 10.1, slack 10.2.
please get hal dbus slackbuild build scripts for slackware from: