[PATCH] hal 0.5.9 rc1

Kay Sievers kay.sievers at vrfy.org
Mon Mar 5 10:03:11 PST 2007


On 3/5/07, Dan Nicholson <dbn.lists at gmail.com> wrote:
> On 3/5/07, David Zeuthen <david at fubar.dk> wrote:
> > On Mon, 2007-03-05 at 08:30 -0800, arandamandi wrote:
> > > I'm on slackware current
> > > and glibc are 2.3.6
> > > i need glibc 2.4?
> >
> > Yes, you currently need glibc 2.4 for this to work - glibc 2.4 was
> > released about a year ago so I dunno how 'current' Slackware current is.
> > I'd complain to your distro; no point in living in the past :-)
> >
> > FWIW, I'll take patches for earlier versions / workarounds; IIRC the
> > Nokia people also wanted that. Rob?
>
> You can certainly backport the inotify headers for glibc-2.3.6 and
> your kernel headers. In Linuxfromscratch, we used these two patches.
> The first is for the old linux-libc-headers package, and the second we
> just drop into /usr/include/sys/inotify.h. I've never noticed any
> problems with this approach, but YMMV.
>
> http://www.linuxfromscratch.org/patches/downloads/linux-libc-headers/linux-libc-headers-2.6.12.0-inotify-3.patch
> http://www.linuxfromscratch.org/patches/downloads/glibc/glibc-2.3.6-inotify-1.patch
>
> You'd have to talk to Slackware about that. The other option is for
> HAL to ship some local inotify headers. Here's the equivalent in udev.
>
> http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=udev_sysdeps.h;hb=HEAD

Yeah, I did that for udev, because there was not even a devel-release
of glibc at the time I used inotify. I really see no point doing that
today for HAL.

Thanks,
Kay


More information about the hal mailing list