On 12/1/05, Dan Nicholson <[EMAIL PROTECTED]> wrote: > On 12/1/05, Mark Rosenstand <[EMAIL PROTECTED]> wrote: > > I would like it to use inotify, but it doesn't because the headers are > > too old. I never really understood why most (all?) distributors choose > > to use kernel headers that doesn't match the running kernel. > > It's up to the userspace package you're installing to include the > appropriate headers for inotify support. The userspace package cannot > make any assumptions about what kernel you're running or what kernel > your libc is compiled against. That would be insane.
As a follow up to this comment, beagle also uses inotify. I built it with l-l-h-2.6.12.0, and it works fine now that I've upgraded my kernel to 2.6.14. How? beagle (appropriately) includes inotify.h in it's source tree. [11:59 AM [EMAIL PROTECTED] ls beagle-0.1.2/glue/ beagled-utils.c gecko-utils.cpp ioprio-glue.c tomboykeybinder.h eggaccelerators.c gecko-utils.h Makefile.am vmsize-glue.c eggaccelerators.h inotify-glue.c Makefile.in wv1-glue.c eggtrayicon.c inotify.h screensaver-glue.c eggtrayicon.h inotify-syscalls.h tomboykeybinder.c So, your problem is that dovecot is assuming you'll install inotify.h and its friends to /usr/include/linux which is not appropriate. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
