[ddp@zanovar ~]$ uname -a
Linux zanovar.example.com 2.6.32-71.29.1.el6.x86_64 #1 SMP Mon Jun 27
19:49:27 BST 2011 x86_64 x86_64 x86_64 GNU/Linux
[ddp@zanovar ~]$ ls -l /usr/include/x86_64-linux-gnu/sys/inotify.h
ls: cannot access /usr/include/x86_64-linux-gnu/sys/inotify.h: No such
file or directory
[ddp@zanovar ~]$ ls -l /usr/include/sys/inotify.h
-rw-r--r--. 1 root root 3941 Jun 25 08:25 /usr/include/sys/inotify.h


On Wed, Nov 2, 2011 at 5:19 PM, Yi-Huan Chan (Hubert)
<[email protected]> wrote:
> My guess is that, your linux machine is x86_64.
> For my machine (ubuntu 11.10 amd64), the inotify.h is not under
> sys/inotify.h, so the build script will not enable inotify support.
>
> I modify Makeall for my case
>
> diff -r a705659a30d0 src/Makeall
> --- a/src/Makeall       Thu Nov 03 04:39:44 2011 +0800
> +++ b/src/Makeall       Thu Nov 03 05:13:19 2011 +0800
> @@ -68,7 +68,11 @@
>
>     # Checking for inotify
>     if [ "X$OS" = "XLinux" ]; then
> -        ls /usr/include/sys/inotify.h > /dev/null 2>&1
> +        INOTIFY_H_PATH="/usr/include/sys/inotify.h"
> +        if [ "X$MACH" = "Xx86_64" ]; then
> +            INOTIFY_H_PATH="/usr/include/x86_64-linux-gnu/sys/inotify.h"
> +        fi
> +        ls "$INOTIFY_H_PATH" > /dev/null 2>&1
>         if [ $? = 0 ]; then
>             echo "EEXTRA=-DUSEINOTIFY" >> Config.OS
>         fi
>
> On Wed, Nov 2, 2011 at 11:27 PM, Calum <[email protected]> wrote:
>> On 2 November 2011 15:00, dan (ddp) <[email protected]> wrote:
>>> This assumes he's using a linux that supports inotify.
>>
>> There are ones that don't? :)
>>
>

Reply via email to