Ryan Lortie 450e7b1036 configure.ac: tweak inotify check ...

Our check for inotify_init1() being defined is broken.  We happily
declare that inotify is supported, even if the check fails.

This was originally intended to check for inotify_init1 in the libc so
that we could fall back to inotify_init if it was not yet defined.

FreeBSD has a libinotify that emulates the inotify API via kqueue.  It
installs a <sys/inotify.h> header and requires linking to -linotify.  We
don't want to falsely detect working inotify in this case.

Treat the lack of inotify_init1() in the libc as a lack of inotify
support.  This requires only a new libc -- we still support old kernels:
in the case that inotify1_init() fails, we fall back to inotify_init().

https://bugzilla.gnome.org/show_bug.cgi?id=724330

2014-02-14 10:42:40 -05:00

..

ginotifydirectorymonitor.c

Updated FSF's address

2014-01-31 14:31:55 +01:00

ginotifydirectorymonitor.h

Updated FSF's address

2014-01-31 14:31:55 +01:00

ginotifyfilemonitor.c

Updated FSF's address

2014-01-31 14:31:55 +01:00

ginotifyfilemonitor.h

Updated FSF's address

2014-01-31 14:31:55 +01:00

inotify-helper.c

Updated FSF's address

2014-01-31 14:31:55 +01:00

inotify-helper.h

Updated FSF's address

2014-01-31 14:31:55 +01:00

inotify-kernel.c

configure.ac: tweak inotify check

2014-02-14 10:42:40 -05:00

inotify-kernel.h

Updated FSF's address

2014-01-31 14:31:55 +01:00

inotify-missing.c

Updated FSF's address

2014-01-31 14:31:55 +01:00

inotify-missing.h

Updated FSF's address

2014-01-31 14:31:55 +01:00

inotify-path.c

Updated FSF's address

2014-01-31 14:31:55 +01:00

inotify-path.h

Updated FSF's address

2014-01-31 14:31:55 +01:00

inotify-sub.c

Updated FSF's address

2014-01-31 14:31:55 +01:00

inotify-sub.h

Updated FSF's address

2014-01-31 14:31:55 +01:00

Makefile.am

Rework the build system for a new tests approach

2013-05-31 23:12:15 -04:00