Antonio Palladini wrote:
> Hello list,
> 
> if i try to compile ecore, i get the following error :
> 
>  ecore_file_monitor_inotify.c:17:25: error: sys/inotify.h: No such file
>  or directory
> 
> configure says :
> 
>  checking whether ecore_file module is to be built... yes
>  checking whether inotify is to be used for filemonitoring... yes
> 
> ecore_file_monitor_inotify.c want to include sys/inotify.h
> but i only have it in :
> 
> /usr/include/linux/inotify.h
> /usr/src/linux-headers-2.6.18-3/include/linux/inotify.h
> /usr/src/linux-headers-2.6.18-4/include/linux/inotify.h
> /usr/src/linux-headers-2.6.18-4-k7/include/config/inotify.h
> /usr/src/linux-headers-2.6.18-4-k7/include/linux/inotify.h
> 
> If i change in ecore_file_monitor_inotify.c at line 17
> from :
>  include <sys/inotify.h>
> to:
>  include <linux/inotify.h>
> 
> ecore compiles.
> 
> IIRC sys/ is the correct directory, so something is wrong on my system
> but i don't know what.
> 
> My system is Debian unstable with kernel 2.6.18-4-k7
> 
> any help would be nice
> 
> thank you 
> 
I ran into the same problem. AFAIK inotify.h was moved to the glibc
system headers, I think because it is considered bad to include kernel
headers. However this only happened for glibc 2.5 and debian unstable is
still using 2.3 something. So you can either use libc from debian
experimental, which might give you problems with other packages, disable
inotify support, or use your fix, which I think shouldn't give you
problems ATM.

Cheers
Jochen

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to