Hi there,

I'm trying to build HAL 0.5.8.1 for VectorLinux 5.8 (Slackware 11 derivative).
So far, I'vs had to upgrade Glib2, which I happily did on my Slackware 11 box by using Patrick V's SlackBuild script, and then upgrading the package on VectorLinux (which inherits lots of its libs from Slackware 11).
And then, when I start compiling HAL, I run into these errors:

http://pastebin.com/852923

And after asking at the HAL mailing list, I was told that I need to upgrade Glibc.

"Ok, no problem", or so I thought until I saw Glibc's SlackBuild script.....

Anyway I downloaded the latest Glibc and its extras (v 2.5), and made some ajustments to the script: removing the patches for the 2.3.6 version, except for the locale/timezone patches; changed the versions and tried it.

The configure process would either abort right when it started, or then it wouldn't even start (if the patches weren't applicable).

I have tried to find a prebuilt one on linuxpackges and other popular Slackware 11 package repos, but so far no luck....
Can anyone point me in the right direction, maybe someone with more experience in using/modifying SlackBuild scripts?

Thanks in advance!

I fail to see how this is a glibc problem. Found one other gentoo/german post where someone mentioned the same thing. I'd like to know why people are saying this.

I've built the latest hal just fine on a stock Slackware system. The only thing I upgraded was the kernel headers because hal DOES require 2.6 headers. Give that a whirl and in the future, upgrading glibc is never a good idea, especially when you are jumping so far ahead to a bleeding edge version. If you did manage to get glibc to compile, you would have hosed your entire system after install.

Shame on them....

I just read your 2 posts over on the mailing list. 1.) they didn't suggest you upgrade your glibc, they said to consult your distro. 2.) I missed the part about you running vector. And it seems you are using headers from the kernel tarball via make headers_install but which version is unknown.. Unidef defines aren't necessary either with 2.6.19.1 and I've never installed a unidef package.

First, I would suggest you find a support channel that is Vector Linux based. Vector Linux is not Slackware Linux no matter how much they may be "similar"...

If you have no luck on that front, I don't know what you've done and, how bad you have hosed your system thus far. I would grab the 2.6.19.1 kernel tarball and make a new package below then removepkg on all kernel header stuff and also make sure that /usr/include/{asm,linux} are gone from the system. Make your new header package.

make mrproper
sed -i.bak '/scsi/d' include/Kbuild
make headers_check || :
make headers_install INSTALL_HDR_PATH=/tmp/package-headers/usr

Make sure your system is in a pristine 'stock' state except for the new headers package and then try hal again. But that's just me..

Well, I've already solved it :P

I was getting those make errors because glibc was built against kernel 2.4
I copied the old sg.h include from kernel 2.4 back to /usr/include/scsi, and tried the make again and it worked!

I know. I have tried in the past to build gtk+2 and glib2 upgrades using VL, but it wouldn't work. However, building those same upgrades on S11 works fine, if I use the SlackBuild scripts.

I think the dev team does have plans to fork further from Slackware, for this exact reason....

I'm glad the Glibc beast can stay dormant for now...