--- cvsroot/EV/Makefile.PL	2007/12/22 12:05:42	1.30
+++ cvsroot/EV/Makefile.PL	2009/08/26 17:31:20	1.44
@@ -1,5 +1,6 @@
-use 5.006;
+use 5.008002;
 
+use strict qw(vars subs);
 use Config;
 use ExtUtils::MakeMaker;
 
@@ -45,7 +46,7 @@
 
 EOF
 
-$DEFINE .= " -DEV_USE_MONOTONIC=" . (0 + (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/));
+my $DEFINE .= " -DEV_USE_MONOTONIC=" . (0 + (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/));
 
 print <<EOF;
 
@@ -55,13 +56,12 @@
 POSIX optionally offers support for a (potentially) high-resolution
 realtime clock interface. In a good implementation, using it is faster
 than the normal method of using gettimeofday. Unfortunately, this option
-is also bound to be broken on some systems, so you can disable use and
-probing of this feature altogether here. Otherwise support for this clock
-type will be autodetected at compiletime.
+is also bound to be broken on some systems, and current EV versions do not
+actually call C<gettimeofday> very often, so ti defaults to no.
 
 EOF
 
-$DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "y") =~ /[yY]/));
+$DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/));
 
 print <<EOF;
 
@@ -129,7 +129,9 @@
 
 EOF
 
-$DEFINE .= " -DEV_USE_EPOLL=" . (0 + (prompt ("Enable epoll backend (y/n)?", (-e "/usr/include/sys/epoll.h") ? "y" : "n") =~ /[yY]/));
+my $can_epoll = -e "/usr/include/sys/epoll.h";
+$can_epoll = $ENV{EV_EPOLL} if exists $ENV{EV_EPOLL};
+$DEFINE .= " -DEV_USE_EPOLL=" . (0 + (prompt ("Enable epoll backend (y/n)?", $can_epoll ? "y" : "n") =~ /[yY]/));
 
 print <<EOF;
 
@@ -140,8 +142,11 @@
 many BSD systems. Support for kqueue will be detected at runtime, with a
 safe fallback to other methods when it cannot be used.
 
-Note that kqueue is broken on most operating systems, so it defaults to
-'n' on everything but netbsd. Here is what we know:
+Note that kqueue is broken on most operating systems, so by default it
+won't be used on many platforms, but you can still create your own event
+loop with kqueue backend if you ask specifically for it.
+
+Here is what we know:
 
 NetBSD:  partially working in at least 3.1. Yeah! :)
 FreeBSD: broken on at least 6.2-STABLE,
@@ -153,7 +158,7 @@
 EOF
 
 my $can_kqueue = -e "/usr/include/sys/event.h";
-
+$can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE};
 $DEFINE .= " -DEV_USE_KQUEUE=" . (0 + (prompt ("Enable kqueue backend (y/n)?", $can_kqueue ? "y" : "n") =~ /[yY]/));
 
 print <<EOF;
@@ -181,9 +186,9 @@
 
 EOF
 
-$SOLARIS_LIBS = $^O =~ /solaris/ ? " -lsocket -lnsl" : "";
-
-$LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", "-lpthread -lrt$SOLARIS_LIBS";
+my $solaris_libs = $^O =~ /solaris/i ? "-lsocket -lnsl" : "";
+my $librt = $^O =~ /linux/i ? "-lpthread" : "-lpthread -lrt";
+my $LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", "$librt $solaris_libs";
 
 
 print <<EOF;
@@ -193,12 +198,13 @@
 
 A backend of a different kind is the Linux inotify(7) interface, which can
 be used to speed up (and reduce resource consumption) of stat watchers. If
-you have it, it is usually a good idea to enable it.
+you have the include file and libc support for it, it is usually a good
+idea to enable it, as kernel availability is detected at runtime.
 
 EOF
 
 my $can_inotify = -e "/usr/include/sys/inotify.h";
-
+$can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY};
 $DEFINE .= " -DEV_USE_INOTIFY=" . (0 + (prompt ("Enable inotify support (y/n)?", $can_inotify ? "y" : "n") =~ /[yY]/));
 
 print <<EOF;
@@ -206,6 +212,39 @@
 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
 
 
+Another useful bit of functionality is the Linux eventfd, which is useful
+for faster signal handling (don't care) and intra-thread communications
+(more relevant). Kernel support for this will be probed at runtime, but
+your libc must contain the necessary wrapper. Glibc 2.7 and later should
+have this wrapper.
+
+EOF
+
+my $can_eventfd = -e "/usr/include/sys/eventfd.h";
+$can_eventfd = $ENV{EV_EVENTFD} if exists $ENV{EV_EVENTFD};
+$DEFINE .= " -DEV_USE_EVENTFD=" . (0 + (prompt ("Enable linux eventfd support (y/n)?", $can_eventfd ? "y" : "n") =~ /[yY]/));
+
+print <<EOF;
+
+*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
+
+
+Another sometimes useful bit of functionality is the Linux signalfd, which
+is useful for faster signal handling (don't care). Kernel support for
+this will be probed at runtime, but your libc must contain the necessary
+wrapper. Glibc 2.7 and later should have this wrapper.
+
+EOF
+
+my $can_signalfd = -e "/usr/include/sys/signalfd.h";
+$can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD};
+$DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/));
+
+print <<EOF;
+
+*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
+
+
 EOF
 
 my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 2.6 } ? (AnyEvent => 2.6) : ();
@@ -227,6 +266,7 @@
     LIBS => [$LIBS],
     PREREQ_PM => {
        @anyevent,
+       "common::sense" => 0,
     },
     VERSION_FROM => "EV.pm",
     PM           => {
@@ -234,7 +274,13 @@
     		    'EV/EVAPI.h'	=> '$(INST_LIBDIR)/EV/EVAPI.h',
     		    'EV/MakeMaker.pm'	=> '$(INST_LIBDIR)/EV/MakeMaker.pm',
     		    'libev/ev.h'	=> '$(INST_LIBDIR)/EV/ev.h',
+    		    'libev/ev.pod'	=> '$(INST_LIBDIR)/EV/libev.pod',
                  },
+    MAN3PODS => {
+                    'EV.pm'           => '$(INST_MAN3DIR)/EV.$(MAN3EXT)',
+                    'EV/MakeMaker.pm' => '$(INST_MAN3DIR)/EV::MakeMaker.$(MAN3EXT)',
+                    'libev/ev.pod'    => '$(INST_MAN3DIR)/EV::libev.$(MAN3EXT)',
+                },
 );